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.

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.