Code Change Review Gate
Code Change Review Gate
Claude CodeCursorGitHub🔌 MCP-ready
Health
80/100
▲ 0
📋 0 copies
Trigger Phrase
Use the Code Change Review Gate skill
Prompt
256 words# QUALITY GATE: Code Change Review Gate
## Purpose
Review code changes for correctness, security, maintainability, test coverage, and unintended behaviour.
## When to Use
Use this when the user needs to: Review code changes for correctness, security, maintainability, test coverage, and unintended behaviour. It is designed for repeatable agent or automation work, not one-off fluffy prompting.
## Inputs Required
- Code diff
- Task brief
- Test results
- Affected files
- Risk tolerance
## Workflow
1. Check whether the change matches the brief
2. Look for security and data-handling issues
3. Verify edge cases and error handling
4. Check tests cover changed behaviour
5. Return blocking and non-blocking feedback
## Output Format
Review report with verdict, blocking issues, suggested fixes, and test gaps.
## Quality Rules
- Ground every claim in supplied inputs or clearly mark it as an assumption.
- Prefer specific fields, examples, and decision points over generic advice.
- Include a test command and pass criteria so the skill can be evaluated.
- Keep the output usable by a human first and automation-ready second.
## Guardrails
- Do not send emails, publish posts, contact leads, change calendars, spend money, delete data, or alter production systems without explicit human approval.
- Do not invent facts, private details, legal claims, prices, or external data.
- For web or profile research, use current sources and separate evidence from inference.
- For connected tools, use the minimum permission needed and log the action taken.
## Test Command
Run this skill on a simple example for Code Change Review Gate and return the expected output structure plus any missing inputs.
## Purpose
Review code changes for correctness, security, maintainability, test coverage, and unintended behaviour.
## When to Use
Use this when the user needs to: Review code changes for correctness, security, maintainability, test coverage, and unintended behaviour. It is designed for repeatable agent or automation work, not one-off fluffy prompting.
## Inputs Required
- Code diff
- Task brief
- Test results
- Affected files
- Risk tolerance
## Workflow
1. Check whether the change matches the brief
2. Look for security and data-handling issues
3. Verify edge cases and error handling
4. Check tests cover changed behaviour
5. Return blocking and non-blocking feedback
## Output Format
Review report with verdict, blocking issues, suggested fixes, and test gaps.
## Quality Rules
- Ground every claim in supplied inputs or clearly mark it as an assumption.
- Prefer specific fields, examples, and decision points over generic advice.
- Include a test command and pass criteria so the skill can be evaluated.
- Keep the output usable by a human first and automation-ready second.
## Guardrails
- Do not send emails, publish posts, contact leads, change calendars, spend money, delete data, or alter production systems without explicit human approval.
- Do not invent facts, private details, legal claims, prices, or external data.
- For web or profile research, use current sources and separate evidence from inference.
- For connected tools, use the minimum permission needed and log the action taken.
## Test Command
Run this skill on a simple example for Code Change Review Gate and return the expected output structure plus any missing inputs.
Before & After
❌ Without this prompt
Make me an automation for code change review gate.
✅ With this prompt
Use the Code Change Review Gate skill. Inputs: goal, systems, data fields, approval owner, and definition of done. Return the workflow, tests, guardrails, and approval checkpoint.
Install Instructions
Copy the body into Prompt Hub as a quality-gate. For Agent Skills, save as SKILL.md or paste into the target agent/project. For n8n/Make/Voiceflow, use this as the build blueprint before importing any third-party JSON.
Test It
Test command:
Run Code Change Review Gate with a tiny dummy case and verify it returns the declared output format, missing-input warnings, guardrails, and pass criteria.
Expected output:
Review report with verdict, blocking issues, suggested fixes, and test gaps.
Pass criteria:
- Passes when the output is specific, complete, safe, testable, approval-aware where needed, and immediately usable with light editing.
⚠️ Guardrails
- Human approval is required before external sends, publishing, destructive changes, spending money, calendar booking, CRM updates that change customer status, or production system changes. Use least-privilege tool access.
📁 Context File Tip
Source context: Sabrina Ramonov describes agents.sabrina.dev as a free library of AI agents and automations, including n8n and Make templates. Related source: https://agentskills.io/home. Agent-skill structure context: https://agentskills.io/home. Security context: https://arxiv.org/abs/2510.26328.
⚡ Automation
Claude Code|Cursor|GitHub
🔌 MCP-compatible