← ClaudeAtlas

code-review-expertlisted

Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
createusernam/setup_project · ★ 0 · Code & Development · score 62
Install: claude install-skill createusernam/setup_project
# Code Review Expert ## Overview Perform a structured review of the current git changes with focus on SOLID, architecture, removal candidates, and security risks. Default to review-only output unless the user asks to implement changes. ## Severity Levels | Level | Name | Description | Action | |-------|------|-------------|--------| | **P0** | Critical | Security vulnerability, data loss risk, correctness bug | Must block merge | | **P1** | High | Logic error, significant SOLID violation, performance regression | Should fix before merge | | **P2** | Medium | Code smell, maintainability concern, minor SOLID violation | Fix in this PR or create follow-up | | **P3** | Low | Style, naming, minor suggestion | Optional improvement | ## Workflow ### 0) Contract check (v2.0+) Before generic review, check for a feature contract: ```bash test -f contract.json && test -f .contract-attestation \ && [ "$(sha256sum contract.json | awk '{print $1}')" = "$(tr -d '[:space:]' < .contract-attestation)" ] ``` If a valid attested `contract.json` is present: 1. **Grade the diff against `contract.json.criteria`** as the primary review. 2. For each criterion: - Run `verify.command` if `verify.method` is `grep`/`test`/`typecheck`/`lint`/`build` — exit 0 = pass. - For `playwright` criteria: note that grading the live behavior is `/build-loop`'s job; here, statically check that the implementation could pass the playwright steps (e.g., the selectors exist, the handlers are wired). -