An agentic skills framework & software development methodology that works.
refactor(skills): trim requesting-code-review, keep review guards as a table
Jesse Vincentcfb6281371ef
diff --git a/skills/requesting-code-review/SKILL.md b/skills/requesting-code-review/SKILL.mdindex 4b8aa605f..fa4f2f996 100644--- a/skills/requesting-code-review/SKILL.md+++ b/skills/requesting-code-review/SKILL.md@@ -5,7 +5,7 @@ description: Use when completing tasks, implementing major features, or before m# Requesting Code Review-Dispatch a 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.+Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.**Core principle:** Review early, review often.@@ -72,20 +72,12 @@ You: [Fix progress indicators][Continue to Task 3]```-## Integration with Workflows+## Common Rationalizations-**Subagent-Driven Development:**-- Review after EACH task-- Catch issues before they compound-- Fix before moving to next task--**Executing Plans:**-- Review after each task or at natural checkpoints-- Get feedback, apply, continue--**Ad-Hoc Development:**-- Review before merge-- Review when stuck+| Excuse | Reality |+|--------|---------|+| "I'll just review the diff myself instead of dispatching a reviewer" | You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you. |+| "The reviewer needs my whole session history to understand the change" | Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process. |## Red Flags