Stacks
When it runs, and how it does the job.
A workflow starts a coding agent when GitHub sees a label, a pull request, or a new issue. A skill is the instruction file that agent reads. A stack is the pair, with both files to paste into your repo.
GitHub event
Label, PR, issue
Workflow
Decides when the agent runs
- .github/workflows/<name>.yml
Skill
Decide how it does the job
- .claude/skills/<name>/SKILL.md
- Copy-paste setup
Stack 01
Label-driven dev loop with review skills
The label-driven triage, plan, implement, and red-team loop, with the code-review, testing-strategy, and debug skills named for the agents doing that work. The workflow has not been executed; cost on the workflow page is still an estimate.
GitHub event
Label
Workflow
Decides when the agent runs
- .github/workflows/label-driven-dev-loop.yml
Skills
Decide how it does the job
- .claude/skills/code-review/SKILL.md
- .claude/skills/testing-strategy/SKILL.md
- .claude/skills/debug/SKILL.md
- Copy-paste setup
Stack 02
Security review with the code-review skill
The OWASP-focused pull-request workflow paired with the code-review skill. The workflow YAML is checked against vendor docs and has not been executed.
GitHub event
Pull request
Workflow
Decides when the agent runs
- .github/workflows/claude-security-review.yml
Skill
Decide how it does the job
- .claude/skills/code-review/SKILL.md
- Copy-paste setup
Stack 03
CI failure diagnosis with the debug skill
The failing-CI workflow paired with the debug skill. Linking a workflow_run back to its pull request is still an open caveat, and the workflow has not been executed.
GitHub event
CI failure
Workflow
Decides when the agent runs
- .github/workflows/claude-ci-failure-fix.yml
Skill
Decide how it does the job
- .claude/skills/debug/SKILL.md