Skip to content
Skills Library
Programming · Review & audit

requesting-code-review

/requesting-code-review

Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.

Repository
ai-settings ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.

Original author description

Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.

How it works

  1. Default
  2. Review Package
  3. Handling Findings
Original SKILL.md headings · 44 lines, 196 words
SKILL.md preview
---
name: requesting-code-review
version: 6.2.0
category: workflow
description: Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.
---

# Requesting Code Review

Independent review is a targeted risk control, not a ceremony after every task.

Read `../using-superpowers/references/risk-policy.md`.

## Default

- Low and medium risk: self-review the complete diff.
- High risk or cross-boundary: at most one independent review of the completed
  change.
- Explicit user request: review the requested scope once.

Do not dispatch a reviewer after each task, for mechanical changes, or merely
because subagents are available.

## Review Package

Give the reviewer:

- exact requirements;
- base and head revisions or the precise diff;
- changed boundaries and known risks;
- verification already run;
- a request for only correctness, security, data-loss, contract, and material
  maintainability findings.

Do not pass arbitrary conversation history. Do not ask the reviewer to rerun
passing checks without a concrete reason.

## Handling Findings

1. Verify each finding against the code and requirements.
2. Fix confirmed critical or important issues.
3. Verify the fix with the closest applicable check.
4. Stop. Request one scoped re-review only when the fix is itself high-risk or
   cannot be verified directly.

Minor style preferences do not start another loop. Disputed findings are
adjudicated by technical evidence, not reviewer repetition.

Template: [code-reviewer.md](code-reviewer.md)
Files in this package (3)
  • CHANGELOG.md 1 KB
  • SKILL.md 2 KB
  • code-reviewer.md 1 KB

Versions

RepositoryScoreLicence
This page · tsergeytovarov/ai-settings90MIT
GanyuanRan/Aegis100MIT
event4u-app/agent-config100MIT
osmontero/opencode-skills100MIT
jjuraszek/pi-gauntlet100MIT
seaworld008/commonly-used-high-value-skills100MIT
FrancoStino/opencode-skills-collection100MIT
nikospavlopoulos/devops-mutant-powers100MIT
coco-research/coco100MIT

Database snapshot: 13.11.2026 · package version e08eb8349a8b (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

  • 100loom-requesting-code-review
    Prepare a code review request with change summary, self-test results, and focus areas for reviewers. Use when: verified changes are ready for reviewer handoff or a PR needs a review request summary.
  • 100requesting-code-review-codex
    Request a high-signal Codex-backed review of a diff or task result. Use when completing tasks, implementing major features, or before merging. Codex-backed variant.
  • 95audit
    Adversarial review of code subsystems or non-code artifacts (design docs, plans, concepts) through parallel analytical lenses. Triggers on 'audit', 'review subsystem', 'audit this design', 'review this plan', 'audit concept', 'check the save system', 'examine the UI code', or…
  • 100review
    This skill should be used when the user asks to 'review changes', 'review my code', 'run a code review', 'review last commit', 'review recent changes', or 'check code against spec'.
  • 100second-opinion
    Gets independent code reviews from Codex or Antigravity for uncommitted changes, branch diffs, and commits. Use when the user requests an external review, a second opinion on code, a codex review, a gemini review, an antigravity review, or /second-opinion.
  • 85code-review
    Evidence-based review of pull requests, branch comparisons, working-tree changes, or selected code across risk, repository standards, and originating requirements. Use when asked to review code, a PR, changes since a fixed point, or to coordinate an explicitly authorized review…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.