reviewing-code
/reviewing-code
Use when reviewing changed code, PRs, diffs, or specific files. Finds evidence-backed defects in security, correctness, tests, reliability, performance, maintainability, and docs. Supports quick, standard, deep, team, and external-review modes, plus a simplify mode for over-engineering and "what can we delete" reviews. NOT for repo-wide architecture review, general codebase exploration, fixing issues (use fixing-code), or improving tests without a code review (use improving-tests).
- Author
- alexei-led ↗
- Repository
- cc-thingz ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 10
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when reviewing changed code, PRs, diffs, or specific files. Finds evidence-backed defects in security, correctness, tests, reliability, performance, maintainability, and docs. Supports quick, standard, deep, team, and external-review modes, plus a simplify mode for over-engineering and "what can we delete" reviews. NOT for repo-wide architecture review, general codebase exploration, fixing issues (use fixing-code), or improving tests without a code review (use improving-tests).
Triggers from the description
Original author description
Use when reviewing changed code, PRs, diffs, or specific files. Finds evidence-backed defects in security, correctness, tests, reliability, performance, maintainability, and docs. Supports quick, standard, deep, team, and external-review modes, plus a simplify mode for over-engineering and "what can we delete" reviews. NOT for repo-wide architecture review, general codebase exploration, fixing issues (use fixing-code), or improving tests without a code review (use improving-tests).
How it works
- Workflow ownership
- Scope
- Modes
- Evidence
- Output
- Platform additions
SKILL.md preview
--- description: Use when reviewing changed code, PRs, diffs, or specific files. Finds evidence-backed defects in security, correctness, tests, reliability, performance, maintainability, and docs. Supports quick, standard, deep, team, and external-review modes, plus a simplify mode for over-engineering and "what can we delete" reviews. NOT for repo-wide architecture review, general codebase exploration, fixing issues (use fixing-code), or improving tests without a code review (use improving-tests). name: reviewing-code --- # Code Review Produce findings, not edits, for the requested diff, PR, changed files, or file list. Read `references/severity-rubric.md` before scoring or reporting: it owns the dimensions, severity, confidence, and score rules. Load a language reference only when a finding needs language or framework semantics; do not read every reference merely because that language is in scope: - C#: `references/csharp.md` - Go: `references/go.md` - Java/Kotlin: `references/java-kotlin.md` - Python: `references/python.md` - Rust: `references/rust.md` - TypeScript: `references/typescript.md` - Web, HTML, CSS, JS, HTMX: `references/web.md` Other languages: use the rubric alone; report reduced coverage if missing language guidance limits the review. ## Workflow ownership This skill owns the finding rubric and domain references. Coding-posture owns the general review checklist. Use Revmux for explicitly requested multi-agent review when installed, and Revdiff for explicitly requested interactive annotations; neither is required for an ordinary review. Do not run several review workflows for one request unless the user asks. ## Scope Use the scope the user named. Otherwise ask one question offering: - uncommitted changes - branch compared to the default branch - specific files or a PR diff Use one git or PR command for the whole review. Without command access, work from the supplied diff and files, and ask for them if absent. No changes in scope: report `Nothing to review.` ## Modes Default is standard. - **Quick**: small, low-risk diffs. Security and correctness; changed lines plus direct context. - **Standard**: security, correctness, and tests; follow callers or callees when a finding needs them. - **Deep**: on request for a thorough, risk, or merge-safety review. All rubric dimensions, including boundary inputs and affected tests. - **Team**: on request for team, parallel, or multi-pass review, or offered for a large diff. Split by dimension or file group, then merge into one report: dedupe by `file:line` plus claim, keep the higher severity only when evidence supports it, and put disagreements under Needs review. - **External**: only when the user explicitly asks for an external, second-model, or second-opinion review. Keep private code local unless the bridge runs locally or the user approved sharing. Rate external output with the same rubric; claims you cannot verify go to Needs review. Report whether it completed, was unavailable, or was skipped and why. - **Simplify**: on request for an over-engineering or "what can we delete" review. Simplicity dimension only. Instead of the Output template, one line per finding: `file:line — <tag> <what>. <replacement>.`, with tags `delete`, `stdlib`/`native` (name the replacement), `yagni`, `shrink`. End with `net: -N lines possible.` or `Lean already. Ship.` ## Evidence - Prove each claim from source or observed checks. A read-only reviewer reports checks to run; the caller or engineer executes them. Do not present a proposed check as a passing result. - If a code-graph tool (GitNexus, codegraph) is installed, use it for caller, impact, and test-coverage questions on broad or public-API changes; a stale index is a coverage gap, not evidence. - Web research is for public facts only (CVEs, official docs). Never send private code or diffs to web tools. - Skip style that project tooling already enforces. List suspicious code outside scope as out of scope instead of widening the review. - Review generated or vendored files only when source generation is in scope. ## Output ```markdown ## Code Review Summary Scope: <description> Depth: quick | standard | deep | team | external Languages: <list> Coverage: complete | partial — <reason> Graph evidence: none | <tool> — <freshness/gaps> External review: not requested | completed | unavailable | skipped — <reason> Score: <N/10 if requested> — confidence <high|medium|low> ### Critical - `file:line` — <category>, confidence <level>. <issue> Scenario: <how it fails>. Fix: <concrete fix>. ### Warnings - `file:line` — <category>, confidence <level>. <issue> Scenario: <how it fails>. Fix: <concrete fix>. ### Suggestions - `file:line` — <category>, confidence <level>. <improvement>. Fix: <concrete fix>. ### Needs review - `file:line or tool/context gap` — <missing context and why it matters>. ### Summary <2-3 sentences: merge risk and next actions, or "No confirmed findings".> ``` Omit empty sections, except Needs review when it explains partial coverage. ## Platform additions No target-specific additions.
Files in this package (10)
- SKILL.md 5 KB
- .agentbundler/targets/claude.json 1 KB
- references/csharp.md 1 KB
- references/go.md 1 KB
- references/java-kotlin.md 1 KB
- references/python.md 1 KB
- references/rust.md 1 KB
- references/severity-rubric.md 5 KB
- references/typescript.md 1 KB
- references/web.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · alexei-led/cc-thingz | 100 | MIT |
| joeblackwaslike/agent-skills | 100 | MIT |
| Montinou/triqual | 100 | MIT |
| thesoftwarehouse/agentic-collections | 100 | MIT |
| julianobarbosa/claude-code-skills | 100 | MIT |
| isvlasov/rageatc-oss | 100 | MIT |
| bostonaholic/rpikit | 100 | MIT |
| bbeny123/pragma | 90 | MIT |
Database snapshot: 13.11.2026 · package version bb83eebbf6a0 (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
- 90code-reviewing
Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge. - 100code-review
Review code for correctness, security, performance, and maintainability. Use when the user asks to "review this code", "check my changes", "review PR", "audit", or "what do you think of this approach". - 90review-code
Review diffs, pull requests, commits, patches, or source files for correctness, baseline security, performance, maintainability, tests, and integration risk. Use for ordinary read-only review, edge-case audits, PR preflight, and reviewer simulation; use audit-code-security when… - 100code-review
Reviews pull requests and code changes for correctness, conventions, maintainability, performance, test coverage, and security. Use when the user asks for a code review, PR review, feedback on a diff, or to check code quality. - 90review
Review changed code for correctness, security, simplicity, maintainability, tests, performance, and approved-spec compliance. Use for pull requests, diffs, implementation reviews, or security-focused code audits. - 100code-review
Reviews code changes, pull requests, and diffs for correctness, security, performance, and style. Use when the user submits a PR for review, asks to review a diff or code snippet, or requests a quality check on recent changes.