fix-review – Coding skill for AI agents
Verify fix commits address audit findings without new bugs
Install the fix-review skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/fix-review-442cc.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /fix-review – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/fix-review-442cc.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $fix-review – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/fix-review-442cc.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /fix-review – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/fix-review-442cc.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /fix-review – then describe the task you want done.
SKILL.md content
Fix Review
Overview
Verify that fix commits properly address audit findings without introducing new bugs or security vulnerabilities.
When to Use This Skill
Use this skill when you need to verify fix commits address audit findings without new bugs.
Use this skill when:
- Reviewing commits that address security audit findings
- Verifying that fixes don't introduce new vulnerabilities
- Ensuring code changes properly resolve identified issues
- Validating that remediation efforts are complete and correct
Instructions
This skill helps verify that fix commits properly address audit findings:
1. Review Fix Commits: Analyze commits that claim to fix audit findings
2. Verify Resolution: Ensure the original issue is properly addressed
3. Check for Regressions: Verify no new bugs or vulnerabilities are introduced
4. Validate Completeness: Ensure all aspects of the finding are resolved
Review Process
When reviewing fix commits:
1. Compare the fix against the original audit finding
2. Verify the fix addresses the root cause, not just symptoms
3. Check for potential side effects or new issues
4. Validate that tests cover the fixed scenario
5. Search reachable related paths for the same root cause; record what was covered and what remains unverified
Evidence record
Bind the review to the exact full head SHA, original finding and affected scope. Record the pre-fix trigger, post-fix behavior, tests actually run, unresolved variants and limitations. A test that cannot run is unverified, not passing. This instruction alone does not satisfy a repository Tessl or maintainer merge gate.
Best Practices
- Review fixes in context of the full codebase
- Verify test coverage for the fixed issue
- Check for similar patterns that might need fixing
- Ensure fixes follow security best practices
- Document the resolution approach
Resources
For more information, see the [source repository](https://github.com/trailofbits/skills/tree/main/plugins/fix-review).
Example
User request:
> Review commits that address security audit findings.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
- fp-async – Practical async patterns using TaskEither - clean pipelines instead of try/catch hell…
- fp-backend – Functional programming patterns for Node.js/Deno backend development using fp-ts…
- fp-errors – Stop throwing everywhere - handle errors as values using Either and TaskEither for…
- fp-pragmatic – A practical, jargon-free guide to functional programming - the 80/20 approach that gets…
- fp-react – Practical patterns for using fp-ts with React - hooks, state, forms, data fetching…
- fp-refactor – Comprehensive guide for refactoring imperative TypeScript code to fp-ts functional…
- fp-taskeither-ref – Quick reference for TaskEither. Use when user needs async error handling, API calls, or…
- fp-ts-errors – Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable…