{"name":"review-code-changes","version":"1.0.0","author":"packary","description":"Catch real defects before code ships","category":"Engineering","tags":["review","security","git"],"rating":0,"review_count":0,"installs":1,"runs":0,"successful_runs":0,"verified":true,"security":"Passed","updated_at":"2026-07-21T07:12:37Z","instructions":"---\nname: review-code-changes\ndescription: Review code changes for concrete, actionable defects before merge or handoff. Use when asked to inspect a diff, staged changes, a branch, or a pull request for bugs, security problems, regressions, and missing tests.\n---\n\n# Review Code Changes\n\nInspect the requested change in repository context. Read the diff first, then the surrounding code needed to prove or disprove each concern.\n\n## Workflow\n\n1. Confirm the review scope from the user's request; otherwise use current unstaged and staged changes.\n2. Inspect repository guidance and relevant tests.\n3. Trace changed inputs, state transitions, failure paths, and external effects.\n4. Run focused read-only checks when they materially improve confidence.\n5. Report only issues introduced or exposed by the change that the author can act on.\n\nPrioritize correctness, security, data loss, concurrency, broken user flows, and missing validation. Avoid style-only feedback unless it causes a functional defect.\n\nFor each finding, give a short title, exact file and line, severity, the failure scenario, and a practical fix direction. If no actionable defects are found, say so and state any verification limits.\n","permissions":["read repository files"],"compatible_with":["Codex","Claude Code","Cursor","Gemini CLI","Hermes","OpenClaw"],"privacy":"Execution payloads are processed transiently and are not stored","retention":"zero-retention"}