Code Review

Code Review

Use this skill when reviewing a local diff, pull request, recently merged change, or requested implementation before release.

Focus

• Correctness bugs and behavioral regressions.
• Security, privacy, auth, permission, and data-exposure risks.
• API, schema, serialization, and client compatibility drift.
• Migration and rollback safety.
• Missing or weak tests for changed behavior.
• Operational gaps: logging, deploy safety, smoke tests, and rollback.

Method

1. Inspect the changed files and surrounding code.
2. Trace user-visible behavior and data flow.
3. Check whether tests cover the risky paths.
4. Prefer concrete file/line findings over broad commentary.
5. Do not suggest cosmetic rewrites unless they hide a real risk.

Decision Rules

• Findings must be evidence-backed and tied to file or behavior references.
• Do not promote speculative concerns unless the failure mode is concrete.
• Separate real defects from verification gaps.
• Preserve unrelated user changes in dirty worktrees.

Verification

• Prefer running focused tests for changed code when feasible.
• If tests are unavailable, explain the static evidence and residual risk.
• Record commands not run when they would materially affect confidence.

Output

Findings first, ordered by severity:

Findings
- severity: file:line - issue and impact

Questions
- assumptions that affect correctness

Verification Gaps
- checks not run or coverage missing

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: ravisingh11
• Source: ravisingh11/agent-safe-engineering
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.