bug code review

    1

    Senior-level code review for bug fix branches with regression analysis and manual verification plans.

    Free

    4 installsSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    bug code review

    Example session with this skill installed

    Review the bug fix branch fix/auth-token-leak. Check if it fixes the logging issue reported in JIRA-402 and provide a manual test plan.

    • Read your context and instructions
    • Compiled the bug code review

    I have reviewed the changes in fix/auth-token-leak against main. The fix correctly addresses the sensitive data leak in the middleware logger but requires one critical adjustment regarding exception handling.

    Bug Fix Review: fix/auth-token-leak

    SeverityFileLineDescriptionWhy it mattersSuggested Improvement
    Criticalsrc/middleware/logger.ts42The catch block logs the raw error object, which still contains the Authorization header if the request fails during parsing.This negates the fix for failed requests, potentially leaking tokens to the log aggregator.log.error({ err: scrub(err) }, "Request failed");
    Minorsrc/utils/scrubber.ts15The regex for token identification is case-sensitive.Tokens passed as authorization (lowercase) might bypass the filter.Use the /i flag in the RegExp.

    Summary Judgment: DO NOT MERGE. The fix is incomplete because it ignores the error-handling path.

    Blockers:

    1. Fix the error block in logger.ts to ensure the scrubber is applied to exception objects.
    2. Add a regression test specifically for a malformed request that triggers an exception.

    Manual Tests

    1. Verification of Fix

    • Setup: Use nix run .#testbed with the auth-debug profile.
    • Steps:
      1. Start the server: npm run dev.
      2. Send a valid request: curl -H "Authorization: Bearer secret-token" http://localhost:3000/api/data.
      3. Check logs: tail -n 20 logs/app.log.
    • Expected Result: The log line should show "authorization": "[REDACTED]" instead of the cleartext token.

    2. Error Path Regression

    • Setup: Same as above.

    Steps: Send a malformed JSON body with a valid header: curl -X POST -H "Authorization: Bearer secret-token" -d "{invalid" http://localhost:3000/api/data.

    • Expected Result: The error log must not contain "secret-token".

    Next steps

    • Apply the regex case-insensitivity fix to scrubber.ts.
    • Update the middleware catch block to wrap the error object in the scrubber.
    • Re-run npm test to ensure the new regression cases pass.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Reviewing bug fixes requires more than just checking if the code compiles. You need to ensure the root cause is addressed without introducing regressions or performance bottlenecks. This skill conducts a senior-engineer level, production-readiness review of merge requests specifically targeting bug fixes.

    What it does

    • Root cause validation identifies the original bug and verifies the implementation resolves the source, not just the symptom.
    • Regression analysis determines if changes unintentionally impact existing functionality or backward compatibility.
    • Safety and security auditing scans for exception-handling gaps, logging concerns, and potential production risks.
    • Automated test verification checks that new tests would fail without the fix and pass with it, covering unit and integration layers.
    • Manual verification planning generates concrete, step-by-step instructions for humans to verify the fix in a real environment.

    How it works

    1. Context gathering triggers a script or manual git commands to extract the diff stat, commit history, and ticket references.
    2. Analysis phase reads the changed functions in full along with their callers to understand the impact beyond the diff hunks.
    3. Execution of tests runs relevant test suites locally to verify the fix and check for side effects.
    4. Structured reporting generates a review following a standardized template with severity levels and code-backed improvements.

    Frameworks & tools

    Works with any language or framework accessible via standard Git workflows. It specifically supports repositories using CLAUDE.md or AGENTS.md for environmental guidance and includes specialized logic for systems utilizing Modbus, Nix, or RES gateway architectures.

    Why this beats prompting it yourself

    Generic prompts often miss the "why" behind a fix or fail to suggest a manual verification plan. This skill enforces a strict multi-dimensional review checklist that ensures edge cases, performance regressions, and safety risks are never skipped.

    Use cases

    • Reviewing a critical hotfix branch before merging into the production branch.
    • Auditing a junior developer's PR to ensure they followed project-specific testing conventions.
    • Generating a manual QA plan for a complex bug that automated tests cannot fully replicate.

    Known limitations

    Requires a local Git environment and access to the repository's history. Automated test execution depends on the local environment having the necessary dependencies installed.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    4 installs

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 9 days ago

    • Free to download with an account

    Listed9 days ago

    What's inside

    Frequently Asked Questions