.claude/skills/receiving-code-reviewRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/receiving-code-reviewRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/receiving-code-reviewRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/receiving-code-reviewRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @eohmig/receiving-code-reviewclawhub inspect @eohmig/receiving-code-review --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:4a78b8dc08452ca0e5f4f0b430f899cb4f8c7789049e72fe48b952b6db97bdddskill-card.mdSKILL.mdInitial release of the "receiving-code-review" skill. - Guides on handling code review feedback with technical rigor, not performative agreement. - Step-by-step process: read, understand, verify, evaluate, respond, implement. - Explicit list of forbidden responses (no empty praise or thanks). - Detailed instructions for external vs. internal feedback handling. - YAGNI and implementation order checks. - Clear process for pushing back on incorrect or unclear suggestions. - Examples of good and bad replies. - Special instructions for replying to GitHub review comments in threads.