full-code-review skillA
full-code-review is agent-read markdown (skill) from office-kit/pptx: Use before opening a PR to do a maintainer-perspective review of a branch. Walks through "why does this exist", "is the design right", "is the implementation correct", and "are tests / docs / changelog complete". Invoked when the user says "review my branch", "do a full review", "is this PR ready", or "/full-code-review"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Full code review
Before opening a PR — or before merging your own — review the branch as if you were
a maintainer who didn't write it. The author's view is "what I built"; the
maintainer's view is "what this costs forever." This skill walks the second view.
The skill is **collaborative**: each phase produces a finding, you and the user
agree on what to do about it, and only then do you move to the next phase. Do not
batch all phases and dump the result at the end.
## Step 0 — Establish the baseline
Decide what you're comparing against and what the diff actually contains.
```bash
# Determine the base branch (in priority order):
# 1. User explicitly said "compare against X" → use X
# 2. PR exists → gh pr view <num> --json baseRefName
# 3. Default → origin/main (or the project's primary branch)
git fetch origin
git diff --stat ${BASE}...HEAD
git log --oneline ${BASE}...HEAD
git diff --name-only ${BASE}...HEAD
```
Categorize the changed files (use whatever buckets fit the project):
- Public API surface (entry points, type exports)
- Internal implementation
- Tests
- Documentation
- Build / CI / tooling
- Dependencies (lockfile, package manifests)
…Read the whole file at its exact version.
How to install
mdr add office-kit/pptx/full-code-review@git:20260514.7b45fd7mdr add office-kit/pptx/full-code-review@sha256:8a5827852b005f94Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_4n5fjgnhyskzxd7l)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260514.7b45fd7 latest | 2026-05-14 | 7b45fd7 | 10,886 B | A | view · diff |
| git:20260514.f87e12d | 2026-05-14 | f87e12d | 10,773 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10886 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 curl or wget piped into a shell
- 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 link to a raw IP address
- pass: No script tag
Source
office-kit/pptx · 14 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4n5fjgnhyskzxd7l GET https://markdownregistry.com/api/v1/resolve?ref=office-kit/pptx/full-code-review GET https://markdownregistry.com/api/v1/blob/8a5827852b005f94cdb866ef54e4a5d2d10124323b8490ce6e07a788fc03365d
Your agent 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.