code-reviewlisted

Reviews pull requests, git diffs, branches, and code changes for bugs, regressions, repository guideline violations, and high-confidence risks. Use when the user asks for a code review, PR review, pull request review, review of changes, review this diff, or wants automated review feedback before merge. For GitHub pull requests, requires the GitHub CLI (`gh`) authenticated in the target repository.
Firzus/agent-skills · ★ 0 · Code & Development · score 72

Install: claude install-skill Firzus/agent-skills

# Code Review Use this skill to review changed code with a senior-engineer stance: find real bugs and risks introduced by the change, avoid noise, and lead with actionable findings. ## Scope Review only the changed behavior unless the user explicitly asks for a broader audit. Do not treat pre-existing issues as findings unless the change makes them newly reachable or worse. For GitHub PRs, require `gh` to be installed and authenticated. Use `gh` for PR metadata, PR diffs, previous PR comments, and posting comments when requested. Use `git` for local diffs, branch history, `blame`, and full commit SHAs. Do not run builds, typechecks, linters, or test suites as part of review unless the user asks. CI should catch compiler, formatter, import, and basic lint failures. ## Workflow 1. Identify the review target: - GitHub PR: inspect it with `gh pr view` and `gh pr diff`. - Local branch or diff: compare against the requested base branch, merge base, or staged/unstaged changes. - If the target is unclear, ask one concise clarifying question. 2. Check whether review should proceed: - Skip closed or draft PRs unless the user explicitly asks. - Skip trivial generated or automated changes unless the user asks. - If you already reviewed the same PR and no relevant changes were added, say so instead of posting duplicate feedback. 3. Gather repository guidance: - Read relevant `AGENTS.md`, `CLAUDE.md`, Cursor rules, contribution docs, and review