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:
Install
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://github.com/mattpocock/skills/blob/main/skills/engineering/code-review/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.