code-review

Guides requesting code reviews and responding to feedback with technical verification.

1|Updated Jul 18, 2025
One-click install
npx skills add https://github.com/gusgad/service-agent-by-sap --skill code-review-gusgad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/gusgad/service-agent-by-sap/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/gusgad/service-agent-by-sap --skill code-review-gusgad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often fail in two ways: poorly scoped review requests that lack context, and reflexive agreement with feedback that may be wrong for the codebase. This Skill provides discipline for both sides of the review process so feedback is verified against the actual code before being implemented. ## Core Features & Use Cases - Scoped Review Requests: Compute the exact diff boundary with git merge-base, state the intent behind the change, and review incrementally after each meaningful task instead of one giant diff. - Feedback Verification Workflow: Read, restate, verify against the codebase, evaluate for stack-specific constraints (multi-tenant Postgres/Sequelize, Kafka, Angular), then respond with acknowledgment or reasoned pushback. - Ordered Implementation: Clarify all unclear items first, fix blocking issues (security, data integrity, tenant isolation) before simple fixes, and verify after each change. - Use Case: After finishing a bug fix touching tenant-isolated job data, request a scoped review of just that diff, then evaluate each piece of reviewer feedback against the working code before implementing anything. ## Quick Start Ask the agent to review the changes on the current branch against main and help respond to the resulting feedback one item at a time.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I ask for clarification instead of implementing feedback?▼

Stop and ask whenever any item in a batch of feedback is unclear, since items are often related and partial understanding produces wrong implementations. Also ask when you cannot verify a claim either way.