Ci review
Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.
npx -y skills add yarlson/yarstack --skill ci-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Audit CI workflow architecture and effectiveness without modifying it. Use when triggers, jobs, commands, quality gates, caches, artifacts, matrices, permissions, release paths, or deployment automation may be stale, redundant, unsafe, or unjustified.
SKILL.md
1.7 KB, as published. Nobody here has run it
CI Review
Own automation topology and evidence that each component protects a real contract.
Workflow
- Confirm repository scope, comparison target, supported platforms, required-check ownership, and whether remote run evidence is authorized.
- Map triggers, jobs, called commands, environments, permissions, secrets, caches, artifacts, release paths, deployment paths, and required checks.
- Identify each component's consumer and enforced contract using repository and authorized run evidence.
- Find duplicated logic, mismatched versions, ineffective filters, unused matrices, ignored results, retry-masked flakes, dead paths, unjustified permissions, and caches or artifacts without consumers.
- Classify actionable items as
keep,simplify,merge,fix,remove, orowner decision. - Delegate tool provenance to
dependency-review, exploit paths tosecurity-review, infrastructure semantics toinfra-review, runtime readiness torollout-readiness-review, and behavioral test sufficiency totest-gap-review.
For each finding report location, affected contract, evidence, consequence, recommended disposition, change risk, and verification. Recommendations do not authorize implementation.
Do not fetch remote evidence without authority, remove a safety gate on speculation, add scanners for appearance, or rewrite workflows broadly.
Finish with prioritized findings or no-findings, scope, evidence limits, and the smallest advisory cleanup sequence.