Name: receiving-review
Author: wzc520pyfm

Imported from wzc520pyfm/harless (packages/cli/src/templates/modules/skills/skills/receiving-review/SKILL.md). Install upstream with npx skills add wzc520pyfm/harless --skill receiving-review. Copyright stays with the author.

Receiving Code Review

When to use

When someone provides feedback on your code. The goal is to improve the code, not to agree performatively.

Procedure

Read all comments first. Understand the full picture before responding to any individual point.
Classify each comment.
- Correctness issue → must fix.
- Style/convention → follow the project's existing convention.
- Suggestion → evaluate on merit; it's OK to disagree with evidence.
- Question → answer clearly with code references.
Verify before implementing. If a suggestion seems wrong, test it before saying so. "I tried X and it causes Y" is better than "I don't think that's right."
Fix in minimal scope. Address the review point without introducing unrelated changes.
Re-verify. After all fixes, run the full test suite. Use the verification-before-completion skill.

Anti-patterns

Blindly implementing every suggestion without understanding why.
Agreeing with feedback you haven't verified ("good catch, fixed!").
Making defensive arguments without evidence.
Bundling unrelated improvements into the review-fix commit.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install receiving-review and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wzc520pyfm-harless-receiving-review", "kind": "skill", "name": "receiving-review", "description": "Use when receiving code review feedback. Requires technical rigor and verification, not performative agreement or blind implementation.", "publisher": "wzc520pyfm", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when receiving code review feedback. Requires technical rigor and verification, not performative agreement or blind implementation." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/wzc520pyfm/harless", "path": "packages/cli/src/templates/modules/skills/skills/receiving-review/SKILL.md", "ref": "eb57a87e08a98e51b3607def66f0330a55f62069", "url": "https://github.com/wzc520pyfm/harless/blob/eb57a87e08a98e51b3607def66f0330a55f62069/packages/cli/src/templates/modules/skills/skills/receiving-review/SKILL.md", "key": "wzc520pyfm/harless/packages/cli/src/templates/modules/skills/skills/receiving-review/SKILL.md" } }, "instructions": "# Receiving Code Review\n\n## When to use\n\nWhen someone provides feedback on your code. The goal is to improve\nthe code, not to agree performatively.\n\n## Procedure\n\n1. **Read all comments first.** Understand the full picture before\n responding to any individual point.\n2. **Classify each comment.**\n - Correctness issue → must fix.\n - Style/convention → follow the project's existing convention.\n - Suggestion → evaluate on merit; it's OK to disagree with evidence.\n - Question → answer clearly with code references.\n3. **Verify before implementing.** If a suggestion seems wrong, test\n it ", "cost": { "context_tokens": 290 } }

receiving-review

About

Receiving Code Review

When to use

Procedure

Anti-patterns

Use it

Install receiving-review and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews