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:
Quick answer
Receiving Code Review is a free Muse skill for handling review feedback with technical rigor. Its rules are simple: verify before implementing, ask before assuming, and push back with reason, with no performative agreement. That keeps reviews honest and code better, instead of merging changes nobody really believed in.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit bb92a77Step 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: 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://raw.githubusercontent.com/obra/superpowers/bb92a77741419a4ab5f06e711a283343f1ada0c3/skills/receiving-code-review/SKILL.md Pinned version: install the code at commit bb92a77741419a4ab5f06e711a283343f1ada0c3 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 "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.
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
- bb92a77 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 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.