Requesting Code Review
Review early, review often: dispatch a reviewer subagent with precisely crafted context, fix Critical now, Important before proceeding
- What
- Review early, review often: dispatch a reviewer subagent with precisely crafted context, fix Critical now, Important before proceeding
- Cost
- Free
- Needs
- an agent harness that can dispatch subagents (Claude Code style); a git repository to review. Companion: obra-receiving-code-review for handling the feedback.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a review-discipline skill: review early, review often. After each task in subagent-driven development, after every major feature, before every merge to main, dispatch a reviewer subagent — with precisely crafted context (a description, the plan or requirements, the base and head SHAs), never your session's history — using the included `code-reviewer.md` template, then act on the verdict: fix Critical issues immediately, Important before proceeding, note Minor for later, push back with reasoning if the reviewer is wrong. It dismantles the two classic excuses: reviewing the diff inline burns the context you need to keep driving the work, and the reviewer doesn't need your whole history — just the work product. By @obra, listed here with credit to its creator. Honest caveats: it assumes an agent harness that can actually dispatch subagents (Claude Code style); the `code-reviewer.md` template lives in the repo and must be fetched with the skill; never skip review because "it's simple". Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an agent harness that can dispatch subagents (Claude Code style); a git repository to review. Companion: obra-receiving-code-review for handling the feedback. Install "Requesting Code Review" for me. Review early, review often: dispatch a reviewer subagent with precisely crafted context (description, requirements, base/head SHAs) via the code-reviewer.md template. Repository: https://github.com/obra/superpowers/blob/main/skills/requesting-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 "obra-requesting-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. 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.