A streamlined workflow to review, triage, and patch findings from previous code audits.
Install
mkdir -p .claude/skills/patch && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12324" && unzip -o skill.zip -d .claude/skills/patch && rm skill.zipInstalls to .claude/skills/patch
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Address /review findings on the uncommitted Ensemble diff. Reads the most-recent review output from context, triages (fix-now is the DEFAULT for any finding about this diff — P0/P1/bounded-P2; escalate to Brandon if it needs a decision or is big; backlog only for genuinely new ideas), presents a fix plan, then patches inline — no agent spawn. Re-runs the gates after. Use after /review, before /done. Plan-first.Key capabilities
- →Load findings from the most-recent /review output in context
- →Triage findings into fix-now, escalate, or backlog categories
- →Present a patch plan including fix sketch and validation gates
- →Apply inline patches with a 'Why:' comment for non-obvious fixes
- →Re-run gates like typecheck, lint, and critique tests after patching
- →Report applied patches, escalated findings, backlogged ideas, and gate status
How it works
The skill loads review findings, triages them based on predefined criteria, and then applies inline code patches or creates issues for findings that require escalation or backlogging.
Inputs & outputs
When to use patch
- →Applying review feedback
- →Fixing code bugs
- →Triage review findings
- →Closing the review-to-done loop
About patch
Processes findings from code reviews, triages them into fix-now or backlog items, and applies patches directly inline to the codebase.
Address /review findings on the uncommitted Ensemble diff. Reads the most-recent review output from context, triages (fix-now is the DEFAULT for any finding about this diff — P0/P1/bounded-P2; escalate to Brandon if it needs a decision or is big; backlog only for genuinely new ideas), presents a fix
When not to use it
- →When the most-recent /review output is not in context
- →When a finding requires a design call or is large/cross-cutting
- →When a finding contradicts a project memory note
Limitations
- →Cannot patch files not flagged by the most-recent /review
- →Cannot silently downgrade a P0 finding
- →Does not run reviewers; that is /review's job
How it compares
This workflow directly integrates review feedback into the codebase by applying inline patches and managing follow-up actions, unlike a manual process that would involve separate steps for triage, coding, and issue tracking.
Compared to similar skills
patch side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| patch (this skill) | 0 | 5mo | No flags | Intermediate |
| python-testing-patterns | 77 | 5mo | Review | Intermediate |
| dependency-upgrade | 26 | 8mo | Review | Intermediate |
| test-cases | 57 | 10mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
test-cases
cexll
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
wcag-audit-patterns
wshobson
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
code-coverage-with-gcov
gadievron
Add gcov code coverage instrumentation to C/C++ projects