deadeye-pr SKILL.md skillC
deadeye-pr from deepaksinghcs14/deadeye-cc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add deepaksinghcs14/deadeye-cc/deadeye-pr@git:20261016.c0607b8Pins git:20261016.c0607b8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- C, 15 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- deepaksinghcs14/deadeye-cc
- Path
skills/deadeye-pr/SKILL.md- Versions recorded
- 17
- Latest version
- git:20261016.c0607b8, committed Oct 16, 2026
- First version recorded
- Sep 2, 2026
- Size
- 29,754 bytes
- Repository stars
- 6
- License
- MIT
PR review across four lenses -- over-engineering, correctness, performance, security -- printed locally, opt-in to post.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- 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 …
Read the whole file at its exact version.
How to install
mdr add deepaksinghcs14/deadeye-cc/deadeye-pr@sha256:136f687960be2b65The line at the top of this page pins the label git:20261016.c0607b8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nu7p42lh4ye5qxxk)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 17 versions of this file, between Sep 2, 2026 and Oct 16, 2026, about one every 3 days. Its first recorded version is graded B and its latest C.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c0607b8 latest | 2026-10-16 | c0607b8 | 29,754 B | C | view · diff |
| git:20261016.22a761d | 2026-10-16 | 22a761d | 29,594 B | C | view · diff |
| git:20261011.1bd9f18 | 2026-10-11 | 1bd9f18 | 28,718 B | C | view · diff |
| git:20260929.817b05c | 2026-09-29 | 817b05c | 27,130 B | C | view · diff |
| git:20260921.3c022a7 | 2026-09-21 | 3c022a7 | 26,415 B | C | view · diff |
| git:20260913.e21ccd0 | 2026-09-13 | e21ccd0 | 23,478 B | C | view · diff |
| git:20260913.4ef468e | 2026-09-13 | 4ef468e | 23,343 B | C | view · diff |
| git:20260911.b42e026 | 2026-09-11 | b42e026 | 22,041 B | C | view · diff |
| git:20260911.fe816ca | 2026-09-11 | fe816ca | 21,766 B | C | view · diff |
| git:20260909.51b5bf9 | 2026-09-09 | 51b5bf9 | 21,778 B | C | view · diff |
| git:20260908.a8c1927 | 2026-09-08 | a8c1927 | 21,369 B | C | view · diff |
| git:20260908.9e16456 | 2026-09-08 | 9e16456 | 21,200 B | C | view · diff |
| git:20260904.f2cd552 | 2026-09-04 | f2cd552 | 21,068 B | C | view · diff |
| git:20260902.3a6be38 | 2026-09-02 | 3a6be38 | 19,067 B | C | view · diff |
| git:20260902.d7860b0 | 2026-09-02 | d7860b0 | 19,203 B | C | view · diff |
| git:20260902.51473c6 | 2026-09-02 | 51473c6 | 14,628 B | C | view · diff |
| git:20260902.f6f9654 | 2026-09-02 | f6f9654 | 13,450 B | B | view |
Audit of the latest version
- fail: No curl or wget piped into a shell (matched: curl | sh)
- fail: No link to a raw IP address (matched: http://169.254.169.254)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (29754 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
deepaksinghcs14/deadeye-cc · 6 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nu7p42lh4ye5qxxk GET https://markdownregistry.com/api/v1/resolve?ref=deepaksinghcs14/deadeye-cc/deadeye-pr GET https://markdownregistry.com/api/v1/blob/136f687960be2b65c60b1317b2132719f9481afcf7f5638a737cb5422aa65c35
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.