← ClaudeAtlas

deadeye-prlisted

PR review across four lenses -- over-engineering, correctness, performance, security -- printed locally, opt-in to post.
deepaksinghcs14/deadeye-cc · ★ 5 · Code & Development · score 80
Install: claude install-skill deepaksinghcs14/deadeye-cc
<!-- deadeye-pr: canonical rubric; edit internal/prreview/ruleset.md, the skill and every host rendering are generated from it --> # Deadeye PR Review One shot over a whole pull request: four lenses, one pass, tagged findings. `/deadeye-review` runs this exact four-lens rubric locally against your working diff or the whole repo — this adds what a PR needs on top: resolving a real PR via `gh`, checking what other reviewers already said, huge-PR fan-out, and an opt-in post back to GitHub. `/deadeye-guard` stays the dedicated deep-security pass this lens is drawn from. ## Scope Resolve the target PR, then review only its diff: - An argument (a PR number like `123` or a full PR URL, after stripping `--post`) → that PR. - No argument → the PR for the current branch. - Fetch the diff and metadata with the GitHub CLI: - `gh pr diff <N>` (or `gh pr diff` for the current branch) for the unified diff. - `gh pr view <N> --json title,body,additions,deletions,files,baseRefName,headRefName` for the header. - Read the changed hunks **plus enough surrounding context to judge a trust boundary or a caller contract** — "is this input validated" and "does this break a caller" both need the code around the hunk, not just the `+` lines. Preconditions and graceful degradation: - `gh` not installed or not authenticated → say so plainly and stop, or, if the user has a local branch, offer to review `git diff <base>...HEAD` instead. Do not invent PR contents. - Not a GitHub repo / n