← ClaudeAtlas

code-reviewlisted

Performs self-review during development by checking changed code for bugs, security issues, performance problems, and test gaps. Runs inline before committing or creating PRs. Use when reviewing own code, self-review, check my changes, review before commit, review my code, code review, quality check, or when triggered by incremental-implementation before a PR.
Saturate/agents · ★ 0 · Code & Development · score 63
Install: claude install-skill Saturate/agents
# Code Review Review your own code like a senior engineer would review someone else's. Catch issues before they become PR comments. ## Progress Checklist - [ ] Get the diff - [ ] Detect tech stack - [ ] Review for correctness - [ ] Review for security - [ ] Review for performance - [ ] Check test coverage - [ ] Report findings ## Step 0: Get the Diff ```bash # If reviewing staged changes git diff --cached # If reviewing branch changes git diff main...HEAD # Overview first git diff --cached --stat ``` ## Step 1: Detect Tech Stack Check changed files to determine which review patterns apply: - `.ts`, `.tsx`, `.js`, `.jsx` - Load TypeScript/JavaScript patterns - `.cs`, `.csproj` - Load .NET patterns - `.go` - Load Go patterns - `.vue` - Load Vue patterns Load relevant issue references: - `../pr-review/references/issues-general.md` - Always - `../pr-review/references/issues-typescript.md` - If TS/JS files changed - `../pr-review/references/issues-dotnet.md` - If .NET files changed - `../pr-review/references/issues-go.md` - If Go files changed Also load shared references: - `../_shared/security-checklist.md` - `../_shared/performance-anti-patterns.md` ## Step 2: Review for Correctness For each changed file: - Does the logic actually do what it's supposed to? - Edge cases: null/undefined, empty collections, boundary values, concurrent access - Error handling: are errors caught where they should be? Are they swallowed silently? - Type safety: any type assertions, unch