← ClaudeAtlas

review-codelisted

Review code for correctness, naming conventions, style, error handling, security, and scaling concerns. Use when reviewing code, checking a diff, auditing a function, or asking about code quality, or whether a change to a doc is true. Covers Python, PySpark, SQL, KQL, DAX, TMDL, Fabric pipeline expressions, JavaScript, TypeScript, Lightning Web Components, CSS, Rust, Bash and PowerShell scripts, Claude Code settings and MCP config JSON, GitHub Actions workflows and pre-commit config, and data-engineering patterns. In Markdown it checks only whether changed claims match their sources and whether the change breaks a governing CLAUDE.md, never style.
wardawgmalvicious/claude-plugins · ★ 0 · Code & Development · score 78
Install: claude install-skill wardawgmalvicious/claude-plugins
# Code review Surface findings on code quality across correctness, security, scaling, error handling, naming/style, maintainability, and compliance with the `CLAUDE.md` files that govern each file. **Read-only — never modify code.** You run as a forked subagent: you see none of the caller's conversation, your final message is all it receives, and no one can answer a question. **Target given**: $ARGUMENTS ## 1. Determine review target Pick the first that applies: 1. **The target line above names one** — a diff command (`git diff --cached`, `git diff <base>...<branch>`), a pasted diff, file paths, a function or a ref — use that. Given a diff, review its changed hunks, reading each file around them. 2. **In a git repo with uncommitted changes** — run `git status` then `git diff` (and `git diff --staged`) to scope the review to working-tree changes. 3. **In a git repo, clean tree, on a feature branch** — diff against the merge base: `git diff main...HEAD` (substitute `master` if that's the default). 4. **None of the above** — return `review-code: no target found; pass a diff command, a path or a pasted diff.` and stop. Do not guess. **The target line may carry the change's intent**, after the target, once or more: `intent: #<n>`, an issue in this repo, or `intent: <path>`, a brief file. Read each before reviewing, by `gh issue view <n>` and then `gh issue view <n> --comments`, which prints the comments in place of the body, or by a Read of the path. It is what lets § 2's "N