[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-obra-superpowers-skills-requesting-code-review":3},{"error":4,"detail":5,"metadata":28,"markdownContent":29,"rawMarkdown":25},false,{"repo_full_name":6,"owner":7,"repo_name":8,"repo_forks":9,"skill_path":10,"repo_stars":11,"name":12,"category_id":13,"description":14,"file_tree":15,"skill_md_content":25,"skill_id":26,"skill_key":27},"obra/superpowers","obra","superpowers",7683,"skills/requesting-code-review",96793,"requesting-code-review",1,"Use when completing tasks, implementing major features, or before merging to verify work meets requirements",[16,21],{"name":17,"path":18,"size":19,"type":20},"SKILL.md","skills/requesting-code-review/SKILL.md",2935,"file",{"name":22,"path":23,"size":24,"type":20},"code-reviewer.md","skills/requesting-code-review/code-reviewer.md",3385,"---\nname: requesting-code-review\ndescription: Use when completing tasks, implementing major features, or before merging to verify work meets requirements\n---\n\n# Requesting Code Review\n\nDispatch superpowers:code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.\n\n**Core principle:** Review early, review often.\n\n## When to Request Review\n\n**Mandatory:**\n- After each task in subagent-driven development\n- After completing major feature\n- Before merge to main\n\n**Optional but valuable:**\n- When stuck (fresh perspective)\n- Before refactoring (baseline check)\n- After fixing complex bug\n\n## How to Request\n\n**1. Get git SHAs:**\n```bash\nBASE_SHA=$(git rev-parse HEAD~1)  # or origin/main\nHEAD_SHA=$(git rev-parse HEAD)\n```\n\n**2. Dispatch code-reviewer subagent:**\n\nUse Task tool with superpowers:code-reviewer type, fill template at `code-reviewer.md`\n\n**Placeholders:**\n- `{WHAT_WAS_IMPLEMENTED}` - What you just built\n- `{PLAN_OR_REQUIREMENTS}` - What it should do\n- `{BASE_SHA}` - Starting commit\n- `{HEAD_SHA}` - Ending commit\n- `{DESCRIPTION}` - Brief summary\n\n**3. Act on feedback:**\n- Fix Critical issues immediately\n- Fix Important issues before proceeding\n- Note Minor issues for later\n- Push back if reviewer is wrong (with reasoning)\n\n## Example\n\n```\n[Just completed Task 2: Add verification function]\n\nYou: Let me request code review before proceeding.\n\nBASE_SHA=$(git log --oneline | grep \"Task 1\" | head -1 | awk '{print $1}')\nHEAD_SHA=$(git rev-parse HEAD)\n\n[Dispatch superpowers:code-reviewer subagent]\n  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index\n  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md\n  BASE_SHA: a7981ec\n  HEAD_SHA: 3df7661\n  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types\n\n[Subagent returns]:\n  Strengths: Clean architecture, real tests\n  Issues:\n    Important: Missing progress indicators\n    Minor: Magic number (100) for reporting interval\n  Assessment: Ready to proceed\n\nYou: [Fix progress indicators]\n[Continue to Task 3]\n```\n\n## Integration with Workflows\n\n**Subagent-Driven Development:**\n- Review after EACH task\n- Catch issues before they compound\n- Fix before moving to next task\n\n**Executing Plans:**\n- Review after each batch (3 tasks)\n- Get feedback, apply, continue\n\n**Ad-Hoc Development:**\n- Review before merge\n- Review when stuck\n\n## Red Flags\n\n**Never:**\n- Skip review because \"it's simple\"\n- Ignore Critical issues\n- Proceed with unfixed Important issues\n- Argue with valid technical feedback\n\n**If reviewer wrong:**\n- Push back with technical reasoning\n- Show code/tests that prove it works\n- Request clarification\n\nSee template at: requesting-code-review/code-reviewer.md\n","ce6c277a-4a1e-55e5-9540-9ff9931d4ddb","obra-superpowers-skills-requesting-code-review",{"name":12,"description":14},"\u003Ch1>Requesting Code Review\u003C/h1>\n\u003Cp>Dispatch superpowers:code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.\u003C/p>\n\u003Cp>\u003Cstrong>Core principle:\u003C/strong> Review early, review often.\u003C/p>\n\u003Ch2>When to Request Review\u003C/h2>\n\u003Cp>\u003Cstrong>Mandatory:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>After each task in subagent-driven development\u003C/li>\n\u003Cli>After completing major feature\u003C/li>\n\u003Cli>Before merge to main\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>Optional but valuable:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>When stuck (fresh perspective)\u003C/li>\n\u003Cli>Before refactoring (baseline check)\u003C/li>\n\u003Cli>After fixing complex bug\u003C/li>\n\u003C/ul>\n\u003Ch2>How to Request\u003C/h2>\n\u003Cp>\u003Cstrong>1. Get git SHAs:\u003C/strong>\u003C/p>\n\u003Cdiv class=\"md-code-block\">\u003Cdiv class=\"md-code-lang\">bash\u003C/div>\u003Cpre>\u003Ccode class=\"hljs language-bash\">BASE_SHA=$(git rev-parse HEAD~1)  \u003Cspan class=\"hljs-comment\"># or origin/main\u003C/span>\nHEAD_SHA=$(git rev-parse HEAD)\u003C/code>\u003C/pre>\u003C/div>\u003Cp>\u003Cstrong>2. Dispatch code-reviewer subagent:\u003C/strong>\u003C/p>\n\u003Cp>Use Task tool with superpowers:code-reviewer type, fill template at \u003Ccode>code-reviewer.md\u003C/code>\u003C/p>\n\u003Cp>\u003Cstrong>Placeholders:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>\u003Ccode>{WHAT_WAS_IMPLEMENTED}\u003C/code> - What you just built\u003C/li>\n\u003Cli>\u003Ccode>{PLAN_OR_REQUIREMENTS}\u003C/code> - What it should do\u003C/li>\n\u003Cli>\u003Ccode>{BASE_SHA}\u003C/code> - Starting commit\u003C/li>\n\u003Cli>\u003Ccode>{HEAD_SHA}\u003C/code> - Ending commit\u003C/li>\n\u003Cli>\u003Ccode>{DESCRIPTION}\u003C/code> - Brief summary\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>3. Act on feedback:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Fix Critical issues immediately\u003C/li>\n\u003Cli>Fix Important issues before proceeding\u003C/li>\n\u003Cli>Note Minor issues for later\u003C/li>\n\u003Cli>Push back if reviewer is wrong (with reasoning)\u003C/li>\n\u003C/ul>\n\u003Ch2>Example\u003C/h2>\n\u003Cdiv class=\"md-code-block\">\u003Cpre>\u003Ccode class=\"hljs language-plaintext\">[Just completed Task 2: Add verification function]\n\nYou: Let me request code review before proceeding.\n\nBASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')\nHEAD_SHA=$(git rev-parse HEAD)\n\n[Dispatch superpowers:code-reviewer subagent]\n  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index\n  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md\n  BASE_SHA: a7981ec\n  HEAD_SHA: 3df7661\n  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types\n\n[Subagent returns]:\n  Strengths: Clean architecture, real tests\n  Issues:\n    Important: Missing progress indicators\n    Minor: Magic number (100) for reporting interval\n  Assessment: Ready to proceed\n\nYou: [Fix progress indicators]\n[Continue to Task 3]\u003C/code>\u003C/pre>\u003C/div>\u003Ch2>Integration with Workflows\u003C/h2>\n\u003Cp>\u003Cstrong>Subagent-Driven Development:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Review after EACH task\u003C/li>\n\u003Cli>Catch issues before they compound\u003C/li>\n\u003Cli>Fix before moving to next task\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>Executing Plans:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Review after each batch (3 tasks)\u003C/li>\n\u003Cli>Get feedback, apply, continue\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>Ad-Hoc Development:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Review before merge\u003C/li>\n\u003Cli>Review when stuck\u003C/li>\n\u003C/ul>\n\u003Ch2>Red Flags\u003C/h2>\n\u003Cp>\u003Cstrong>Never:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Skip review because "it's simple"\u003C/li>\n\u003Cli>Ignore Critical issues\u003C/li>\n\u003Cli>Proceed with unfixed Important issues\u003C/li>\n\u003Cli>Argue with valid technical feedback\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>If reviewer wrong:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Push back with technical reasoning\u003C/li>\n\u003Cli>Show code/tests that prove it works\u003C/li>\n\u003Cli>Request clarification\u003C/li>\n\u003C/ul>\n\u003Cp>See template at: requesting-code-review/code-reviewer.md\u003C/p>\n"]