receiving-code-review-skill
について
このスキルは、コードレビューフィードバックを実装前に処理するための構造化されたワークフローを提供します。これは形式的な同意ではなく技術的検証を重視し、開発者に対してコードベースに対して各提案を理解、検証、評価することを要求します。その出力は、技術的に妥当な実装か、具体的な分析に基づいた理由のある反論のいずれかとなります。
クイックインストール
Claude Code
推奨/plugin add https://github.com/Eibon7/roastr-aigit clone https://github.com/Eibon7/roastr-ai.git ~/.claude/skills/receiving-code-review-skillこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
name: receiving-code-review-skill description: Use when receiving code review feedback, before implementing suggestions - requires technical rigor and verification, not performative agreement or blind implementation triggers:
- "review feedback"
- "code review comments"
- "suggestions" used_by:
- orchestrator
- all-agents steps:
- paso1: "READ: Complete feedback without reacting"
- paso2: "UNDERSTAND: Restate requirement (or ask)"
- paso3: "VERIFY: Check against codebase reality"
- paso4: "EVALUATE: Technically sound for THIS codebase?"
- paso5: "RESPOND: Technical acknowledgment or reasoned pushback"
- paso6: "IMPLEMENT: One item at a time, test each" output: "Verified feedback implemented or reasoned pushback" forbidden_responses:
- "❌ 'You're absolutely right!'"
- "❌ 'Great point!' / 'Excellent feedback!'"
- "❌ 'Let me implement that now' (before verification)"
- "✅ Restate technical requirement"
- "✅ Ask clarifying questions"
- "✅ Push back with reasoning if wrong"
- "✅ Just start working (actions > words)" handling_unclear:
- "IF any item unclear → STOP, don't implement"
- "ASK for clarification on unclear items"
- "Items may be related - partial understanding = wrong implementation" pushback_when:
- "Suggestion breaks existing functionality"
- "Reviewer lacks full context"
- "Violates YAGNI (unused feature)"
- "Technically incorrect for this stack"
- "Conflicts with architectural decisions" yagni_check:
- "IF reviewer suggests 'properly' implementing feature"
- "grep codebase for actual usage"
- "IF unused: Remove it (YAGNI)?"
- "IF used: Then implement properly" acknowledging_correct:
- "✅ 'Fixed. [Brief description]'"
- "✅ '[Just fix it and show in code]'"
- "❌ 'You're absolutely right!'"
- "❌ 'Thanks for catching that!'"
- "❌ ANY gratitude expression" bottom_line: | External feedback = suggestions to evaluate, not orders to follow.
Verify. Question. Then implement.
No performative agreement. Technical rigor always. referencias:
- "Fuente: superpowers-skills/receiving-code-review"
- "Roastr: Evita implementar feedback sin verificar"
GitHub リポジトリ
関連スキル
content-collections
メタThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
creating-opencode-plugins
メタThis skill provides the structure and API specifications for creating OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It offers implementation patterns for JavaScript/TypeScript modules that intercept and extend the AI assistant's lifecycle. Use it when you need to build event-driven plugins for monitoring, custom handling, or extending OpenCode's capabilities.
polymarket
メタThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
cloudflare-turnstile
メタThis skill provides comprehensive guidance for implementing Cloudflare Turnstile as a CAPTCHA-alternative bot protection system. It covers integration for forms, login pages, API endpoints, and frameworks like React/Next.js/Hono, while handling invisible challenges that maintain user experience. Use it when migrating from reCAPTCHA, debugging error codes, or implementing token validation and E2E tests.
