Code Review
Two-axis review of your diff — Standards versus Spec — run by parallel subagents so neither masks the other
- What
- Two-axis review of your diff — Standards versus Spec — run by parallel subagents so neither masks the other
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a code-review skill that judges the diff since a fixed point (commit, branch, tag, or merge-base) along two deliberately separate axes, each run by its own subagent so the contexts don't pollute each other. Standards: does the code follow the repo's documented conventions, plus a fixed Fowler smell baseline (Mysterious Name, Duplicated Code, Feature Envy, Data Clumps, Primitive Obsession, Repeated Switches, Shotgun Surgery, Divergent Change, Speculative Generality, Message Chains, Middle Man, Refused Bequest) — always judgement calls, and a documented repo standard always overrides the baseline. Spec: does the code faithfully implement the originating issue or spec — missing requirements, scope creep, and looks-right-but-isn't implementations, each quoting the spec line. The two reports are aggregated side by side, never merged or reranked, ending with per-axis totals and the worst issue within each axis. By @mattpocock, listed here with credit to its creator. Honest caveats: it reads your diff and spawns subagents — fine on a laptop, heavier than a linter; if no spec is found it asks you, and the Spec axis is skipped when there genuinely isn't one; it skips anything your tooling already enforces. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Code Review is a free Muse skill offering a two-axis review of your diff, Standards versus Spec, run by parallel subagents so neither masks the other. It judges the diff since a fixed point, such as a commit, branch, tag or merge-base, along two separate axes, each run by its own subagent so the contexts do not pollute each other.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 49dd158Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Muse account with skill installation enabled Install "Code Review" for me. Two-axis review of your diff — Standards versus Spec — run by parallel subagents so neither masks the other Repository: https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/skills/engineering/code-review/SKILL.md Pinned version: install the code at commit 49dd158d1076134a641b33efb035946536778336 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-code-review". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 49dd158 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Oct 8, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.