Use when reviewing, auditing, or improving GitHub Actions workflows in a repository — checks for version drift, permission issues, missing concurrency controls, path filter gaps, and cross-workflow inconsistencies
From infra-reviewnpx claudepluginhub infraspecdev/tesseract --plugin infra-reviewThis skill uses the workspace's default tool permissions.
checklist.mdtemplates.mdObserves Claude Code sessions via hooks to create atomic project-scoped instincts with confidence scores, evolving them into skills, commands, or agents.
Automatically extracts reusable patterns like error resolutions, workarounds, and debugging techniques from Claude Code sessions via Stop hook, saving them as learned skills for reuse.
Provides patterns for continuous autonomous agent loops with loop selection, quality gates, evals, recovery controls, and failure mitigation. Useful for production AI agent workflows.
Structured review of GitHub Actions workflows for consistency, security, and operational best practices.
Core principle: Workflows in the same repo form a system. Review them as a group, not individually — inconsistencies between workflows cause the hardest-to-debug CI failures.
Read All Workflows + Config -> Evaluate Against Checklist -> Write analysis.md -> Write plan.md -> Ask User to Confirm -> (proceed: Execute / stop: Done / edit: revise plan.md)
Read every file in .github/workflows/ plus related config: release tooling configs (release-please-config.json, .releaserc.json, etc.), versions.tf, .tflint.hcl, package.json.
Run through the 8-point checklist covering version consistency, plugin/config alignment, permissions, concurrency control, path filters, reusable patterns, action pinning, and secrets handling. See checklist.md for detailed criteria, examples, and red flags.
Write findings, checklist results, and a letter grade (A-F) to claude/github-actions-review/analysis.md in the target repo. See templates.md for the full template.
Write actionable implementation steps (or confirm no changes needed) to claude/github-actions-review/plan.md. See templates.md for the full template.
Present: "I've written the analysis (Grade: X) and plan (Y steps). Would you like me to proceed, stop here, or wait while you edit plan.md?"
For each plan step: announce it, execute, show what changed, update verification checkboxes in plan.md, and confirm before moving to the next step. Stop and ask for input if anything fails.
| Mistake | Why It Fails | Do Instead |
|---|---|---|
| Reviewing workflows individually | Misses cross-workflow inconsistencies (version drift, permission gaps) | Always read all workflows before evaluating any |
| Skipping file output on re-review | User loses the updated analysis and grade | Always write fresh analysis.md and plan.md |
| Auto-executing the plan | User hasn't reviewed or approved changes | Always ask for confirmation first |
| Ignoring release tooling config | Plugin mismatches between preview and release workflows go undetected | Read .releaserc.json, release-please-config.json, etc. |
| Checking only permissions at workflow level | Job-level permissions override workflow-level | Check both levels |