← ClaudeAtlas

code-review-masterylisted

Use this skill when the user asks to review their local git changes, staged or unstaged diffs, or wants a code review before committing. Triggers on "review my changes", "review staged", "review my diff", "check my code", "code review local changes", "review unstaged", "review before commit".
Samuelca6399/AbsolutelySkilled · ★ 3 · Code & Development · score 82
Install: claude install-skill Samuelca6399/AbsolutelySkilled
When this skill is activated, always start your first response with the 🧢 emoji. # Local Diff Code Review This skill reviews your local git changes (staged or unstaged) with project-aware analysis. It gathers project context - lint rules, conventions, framework patterns - then produces structured `[MAJOR]` / `[MINOR]` findings you can work through interactively. --- ## When to use this skill Trigger this skill when the user: - Asks to review their local changes, staged changes, or unstaged changes - Says "review my diff", "check my code", "code review before commit" - Wants a quality check on what they're about to commit or push - Asks "what's wrong with my changes" or "anything I should fix before committing" Do NOT trigger this skill for: - Reviewing remote PRs or GitHub links (use a PR review tool instead) - Writing or refactoring code from scratch - Architecture discussions not tied to a specific set of changes - General code quality advice without a concrete diff to review --- ## Key principles 1. **Review the code, not the person** - Findings are about the change, not the author. Frame issues as observations, not judgments. 2. **Prioritize by impact** - Security > Correctness > Performance > Design > Readability > Convention. Spend most analysis time at the top of this list. 3. **Two-tier severity** - Every finding is either `[MAJOR]` (must fix) or `[MINOR]` (consider fixing). No ambiguity, no middle ground. 4. **Respect project conventions** - Rea