github-ci-advisor

• SKILL.mdcore · 3,936 bytes
• references/ci-review.mddoc · 4,088 bytes

# GitHub CI Advisor

## Activation Contract

Use for CI advice, build/test pipelines, audits, security checks, or CI evolution (add, modify, retire). Do not activate automatically during repository bootstrap, and invent no fixed CI manifest or unknown schema fields. It proposes, applies only after explicit approval, and never commits, pushes, releases, deploys, or enables checks or protection.

## Hard Rules

- Discover read-only: read manifests, lockfiles, and script definitions; inspect workflows, triggers, action pins, permissions, and required checks. Use the API for required checks only with authorized, valid access. Never run project scripts, install hooks, or execute downloaded code as discovery.
- Propose from observed commands only: build, typecheck, and tests when they exist, otherwise a smoke check. Ask the human for unset requirements, skip unwanted modules, and never guess a universal CI from an assumed npm project.
- Pin every action to an immutable SHA with human-verified provenance; without verified provenance, stop with unresolved pins and invent no SHA, version, dependency, or code.
- Least privilege: `contents: read`, no secrets to forks, no privileged checkout of a pull-request target. Run untrusted pull-request code only sandboxed without secrets or a writable token; containers reduce risk but are not an absolute sandbox.
- Baseline with a pinned secrets scanner (e.g. a verified-ref Gitleaks action), a secrets-permissions review, and a human read-only repository-safety review. Never claim an action detects prompt injection. Run deterministic scanners only when installed and approved, fetch external evidence only when safe, invent nothing.
- Retire a check only when proven redundant or obsolete; preserve required check names or explicitly warn that branch rules depend on them and need a separate manual change, since branch protection does not manage checks.