Receiving Code Review
Handle review feedback with technical rigor: verify before implementing, ask before assuming, push back with reason — no performative agreement
- What
- Handle review feedback with technical rigor: verify before implementing, ask before assuming, push back with reason — no performative agreement
- Cost
- Free
- Needs
- none — no accounts, keys, or tools required. Used alongside an active code-review flow (e.g. obra-requesting-code-review).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a discipline skill for receiving code review feedback: verify before implementing, ask before assuming, technical correctness over social comfort. It bans performative responses outright ("You're absolutely right!", "Great point!") and replaces them with a read → understand → verify → evaluate → respond → implement loop; unclear items block implementation entirely (partial understanding means wrong implementation); external-reviewer suggestions get checked against codebase reality before being touched, with a YAGNI test for "professional" features ("grepped the codebase — nothing calls it, remove it?"); and it gives the exact phrasing for acknowledging correct feedback and for gracefully correcting a wrong pushback. By @obra, listed here with credit to its creator. Honest caveats: it's a behavioral contract, not tooling — its value depends on the agent actually following the forbidden/allowed response lists; the "your human partner" phrasing assumes a human-in-the-loop workflow. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none — no accounts, keys, or tools required. Used alongside an active code-review flow (e.g. obra-requesting-code-review). Install "Receiving Code Review" for me. It teaches an agent to handle review feedback with technical rigor: verify before implementing, clarify before assuming, push back with reasoning, no performative agreement. Repository: https://github.com/obra/superpowers/blob/main/skills/receiving-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-receiving-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.