github-ci-initlisted

# GitHub CI Init Workflow ## Scope This skill adds **optional, project-specific** GitHub Actions CI workflows to a repository. It complements the `furedea/template-minimal` GitHub template, which already ships the baseline workflows (`gha_lint.yml`, `dependency_review.yml`, `dependency_review_config.yml`, `renovate.json`). It does NOT own **writing or editing the YAML contents of individual workflow files** — that belongs to the `gha-style` skill (permissions minimization, action version pinning, script injection prevention, etc.). ## When to apply vs skip Not every project benefits from these optional workflows. Applying them to a throwaway repo creates maintenance noise (CodeQL alerts on every PR, release-please commits) that outweighs the payoff. ### Apply when - The project has a plausible long-term lifetime (weeks to years) - PRs are expected (from others, or from yourself via feature branches) - The project is public, or likely to become public ### Skip when - It's a throwaway experiment, tutorial follow-along, or one-off script - The project lives in a single commit and won't be touched again - It's a scratch space for exploring a library When in doubt, **skip**. CI can always be added later by running this skill again on the existing repo — that is exactly the retrofit case it is designed for. ## What templates already provide These files are already in GitHub templates and should NOT be added by this skill: - `gha_lint.yml` — actionlint + zizmor (in `tem