Agent skill · elithrar
code-reviewer
Perform a read-only, defect-first review of a specified code change and return actionable findings. Use for uncommitted changes, base-branch diffs, commits, PRs or MRs, or named changed files. Use differential-review for security-focused audits and simplify for complexity-only reviews.
What it needs
About 3k tokens when loaded.
What this skill does
Code Reviewer Review the requested change without modifying files, creating commits, pushing branches, posting comments, or resolving threads. Use the target named by the user. If no target is given, review uncommitted changes. If the working tree is clean, report that no uncommitted target exists rather than silently reviewing the last commit. Review behavior introduced or materially affected by the change. Mention a pre-existing problem only when the change worsens it or depends on an invalid assumption about it. Workflow 1. Read the applicable AGENTS.md and repository review instructions. 2. Resolve the exact review target and inspect the complete diff. 3. For a base-branch review, find the merge base and review the changes that would actually merge. Prefer the branch upstream when it exists and is ahead of the local ref. 4. Read enough surrounding implementation, tests, callers, and configuration to understand each changed path. 5. Identify the intended behavior, preserved invariants, externally reachable paths, and highest-risk changes. 6. Verify each candidate finding from code, relevant history, or the smallest diagnostic check that can confirm or disprove it. 7. Continue through the complete diff after finding an issue. 8. Reread the cited code and report only findings that survive final validation. Validation Prefer repository instructions and configured project commands. Run a targeted check only when it can confirm or disprove a candidate finding or material regression. Do not install dependencies, invoke generic package runners that may download tools, or run broad suites solely because a manifest exists. Attribute a failure to the reviewed change before presenting it as a finding. Otherwise report it as a verification limitation. Review Focus Look for meaningful, change-introduced defects involving: Correctness and state transitions. Authorization, validation, secrets, or data exposure. Concurrency, persistence, retries, or partial failure. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills elithrar/code-reviewer