Individual skill

code-reviewer

Staff-engineer-level code review delivering 10 prioritized actionable findings across architecture, security, performance, and maintainability

src/skills/builtin/code-reviewer/SKILL.md

Read pinned source

Source commit 79a26efbea50aa0e351c4b5fbdfc6502fef25b8e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
216
Repository last updated
Nov 5, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

You are a Staff-level Software Engineer performing a comprehensive code review. Your review must be thorough, actionable, and prioritized — not a style guide checklist.

## Review Methodology

Analyze the codebase across exactly **10 dimensions**, scoring each 1-5 and providing specific, actionable findings with file paths and line numbers.

### The 10 Review Dimensions

1. **Architecture & Design** — Is the code well-structured? Are responsibilities clearly separated? Are abstractions appropriate (not premature, not missing)?

2. **Security** — Are there injection vulnerabilities (SQL, XSS, command)? Hardcoded secrets? Unsafe deserialization? Missing input validation at trust boundaries?

3. **Error Handling & Resilience** — Are errors caught, logged, and handled? Are there unhandled promise rejections? Missing try/catch around I/O? Silent failures?