deep-review

Featured

Review branch diffs, working trees, or PRs in depth with defect, polish and cross-contract coverage. Includes incremental and spec-conformance reviews; excludes fixes, spec-document reviews and quick single-file feedback.

Code & Development 2,894 stars 189 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Deep Review Find actionable defects and improvements with complete selected-hunk and project-rule accounting. Scripts handle discovery, partitions, artifact assembly and validation; the model supplies applicability decisions and evidence-based review. Keep source read-only; write review artifacts under `<out>` (default `.deep-review/<target>/`). Resolve `<skill-dir>` from this file and run bundled commands from the reviewed repository root. ## Contract - No total file or line cap on the PR. Every selected hunk has exactly one defect owner and one polish owner. Both default to broad cohorts of **200 files / 15,000 changed lines per job**, adjustable with `--max-cohort-files`, `--max-cohort-lines`, `--max-polish-files` and `--max-polish-lines`. Oversized files are sliced without losing hunks. An optional `--max-context-lines N` preparation budget accounts for whole-file reading while preserving selection. - Every defect has causal evidence; every advisory has an observed premise, concrete improvement and bounded fix. Investigated rejections stay in the suppression ledger. No quota; advisories never block SHIP. - Every applied rule comes from material actually read, with verbatim text, source, scope and explicit assessment. Root/nested instructions retain scope and precedence. Metadata is a triage queue, not an instruction to load every skill. - Relevant linters run first or reuse evidence for the same frozen inputs. Record unavailable lanes; suppress overlapping findings. ...

Details

Author
compozy
Repository
compozy/compozy
Created
7 months ago
Last Updated
today
Language
Go
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

deep-review

Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.

3 Updated 1 weeks ago
dougcunha
Code & Development Listed

deep-review

Review code, diffs, regressions, and implementation claims by tracing real execution paths. Use when asked to review, audit, or verify code, a change, or a claimed fix. Separates confirmed defects, risks, and improvement suggestions, with specialist lenses for UI click paths, existing test quality, and operator-facing truth surfaces. Read-only by default; fixes need the request or standing project instructions to authorize them, and ticket creation needs an explicit request.

1 Updated 4 days ago
garbageek
Code & Development Listed

deep-review

Review code with one deep single reviewer (Opus at high effort in Claude Code, the session model in Codex) using a bundle of public review best practices - superpowers code-reviewer format, 0-100 confidence scoring, Google eng-practices checklist. Use whenever the user asks to review changes, review code, do a code review, review this branch, review a PR's code, or runs /code-review. This replaces squad-review and agent-skills:code-review for every review.

0 Updated today
amit-mizrachi