code-reviewer
/code-reviewer
How to run code reviews and adversarial reviews. Use when asked to review code, run adversarial review, or when the code review gate blocks.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.05.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
How to run code reviews and adversarial reviews. Use when asked to review code, run adversarial review, or when the code review gate blocks.
Original author description
How to run code reviews and adversarial reviews. Use when asked to review code, run adversarial review, or when the code review gate blocks.
How it works
- Standard Review
- Adversarial Review
- Stop Review Gate Prompt
- Execution Mode
- After Review
SKILL.md preview
---
name: code-reviewer
description: How to run code reviews and adversarial reviews. Use when asked to review code, run adversarial review, or when the code review gate blocks.
category: engineering
tags:
- gobby
metadata:
gobby:
audience: all
depth: 0
---
# Code Reviewer
Run code reviews against local git state. Supports standard review and adversarial review modes.
## Standard Review
Review uncommitted changes or branch diffs:
```bash
# Review uncommitted changes (staged + unstaged)
git diff
git diff --cached
# Review changes against a base branch
git diff main...HEAD
# Review a specific commit
git show <sha>
# List changed files
git diff --name-only main...HEAD
```
## Adversarial Review
Use this prompt template for deeper, skeptical analysis that challenges the change rather than validating it.
### Adversarial Review Prompt Template
```xml
<role>
You are performing an adversarial software review.
Your job is to break confidence in the change, not to validate it.
</role>
<task>
Review the provided repository context as if you are trying to find the strongest reasons this change should not ship yet.
</task>
<operating_stance>
Default to skepticism.
Assume the change can fail in subtle, high-cost, or user-visible ways until the evidence says otherwise.
Do not give credit for good intent, partial fixes, or likely follow-up work.
If something only works on the happy path, treat that as a real weakness.
</operating_stance>
<attack_surface>
Prioritize the kinds of failures that are expensive, dangerous, or hard to detect:
- auth, permissions, tenant isolation, and trust boundaries
- data loss, corruption, duplication, and irreversible state changes
- rollback safety, retries, partial failure, and idempotency gaps
- race conditions, ordering assumptions, stale state, and re-entrancy
- empty-state, null, timeout, and degraded dependency behavior
- version skew, schema drift, migration hazards, and compatibility regressions
- observability gaps that would hide failure or make recovery harder
</attack_surface>
<review_method>
Actively try to disprove the change.
Look for violated invariants, missing guards, unhandled failure paths, and assumptions that stop being true under stress.
Trace how bad inputs, retries, concurrent actions, or partially completed operations move through the code.
</review_method>
<finding_bar>
Report only material findings.
Do not include style feedback, naming feedback, low-value cleanup, or speculative concerns without evidence.
A finding should answer:
1. What can go wrong?
2. Why is this code path vulnerable?
3. What is the likely impact?
4. What concrete change would reduce the risk?
</finding_bar>
<grounding_rules>
Be aggressive, but stay grounded.
Every finding must be defensible from the provided repository context or tool outputs.
Do not invent files, lines, code paths, incidents, attack chains, or runtime behavior you cannot support.
If a conclusion depends on an inference, state that explicitly and keep the confidence honest.
</grounding_rules>
<calibration_rules>
Prefer one strong finding over several weak ones.
Do not dilute serious issues with filler.
If the change looks safe, say so directly and return no findings.
</calibration_rules>
```
## Stop Review Gate Prompt
When the code review gate blocks your stop, review only the immediately previous turn's work:
```xml
<task>
Run a stop-gate review of the previous Claude turn.
Only review code changes from the previous turn — pure status, setup, or reporting output does not count.
Challenge whether that specific work and its design choices should ship.
</task>
<compact_output_contract>
Return a compact final answer.
Your first line must be exactly one of:
- ALLOW: <short reason>
- BLOCK: <short reason>
Do not put anything before that first line.
</compact_output_contract>
<default_follow_through_policy>
Use ALLOW if the previous turn did not make code changes or if you do not see a blocking issue.
Use BLOCK only if the previous turn made code changes and you found something that still needs to be fixed.
</default_follow_through_policy>
<grounding_rules>
Ground every blocking claim in the repository context or tool outputs.
Do not treat the previous Claude response as proof that code changes happened; verify from the repository state.
</grounding_rules>
<dig_deeper_nudge>
If the previous turn did make code changes, check for second-order failures, empty-state behavior, retries, stale state, rollback risk, and design tradeoffs before you finalize.
</dig_deeper_nudge>
```
## Execution Mode
Before running a review, estimate the size:
1. Check `git status --short --untracked-files=all` and `git diff --shortstat`
2. For branch review: `git diff --shortstat <base>...HEAD`
3. Small (1-2 files): review inline
4. Larger or unclear: use a subagent for the review
## After Review
- Present findings verbatim, ordered by severity
- Preserve file paths and line numbers exactly as reported
- **Do NOT auto-fix issues** — ask the user which findings to address
- Don't generate substitute findings if the review tool or process fails
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · GobbyAI/gobby | 100 | Apache-2.0 |
| TerminalSkills/skills | 100 | Apache-2.0 |
| swap-cameroon/kuro-antigravity-config | 100 | MIT |
| a-pavithraa/springboot-skills-marketplace | 100 | MIT |
| borghei/Claude-Skills | 100 | MIT |
| nguyenthienthanh/aura-frog | 100 | MIT |
| yg-codes/srepowers | 100 | MIT |
| basamakcomtr/basamak-skills | 100 | MIT |
| criptogus/agent-evolve-network | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version e7d5a779268c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90reviews
Review a pull request or code change for code health. Use when a user asks to "code review", "review this PR", or "review this change". - 100codex-review
Run Codex code review with Claude's independent double-check. Use when asked \"codex review\", \"review my code with codex\", or wants Codex to review code changes. For adversarial review use /codex-adversarial. - 90receiving-code-review
How to handle code review feedback with technical rigor. Use when receiving review comments from code-reviewer agent, PR reviews, or external feedback. Triggers on: 'review feedback', 'address review', 'fix review comments', 'code review response'. - 90adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary… - 100adversarial-review
Perform a private, evidence-based adversarial review of code, documentation, or agent skills when the user requests a critical review, counterexample search, or pressure test. Supports user-selected reviewer profiles without assuming a provider or model. - 90code-review
Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.