r5

Break down your plan into atomic PRs / プランをatomicなPRに分解する

This skill should be used when the user asks to "research a GitHub repository", "investigate org/repo", "deepwiki research", "analyze repository implementation", "understand how X repo works", or provides an "owner/repo" format GitHub repository name for investigation. Use for researching any GitHub repository's implementation, codebase structure, or internal workings using Deepwiki MCP.

This skill should be used when the user asks to "review a PR", "review pull request", "check this PR", "look at this PR", "is this PR ready to merge", "PRレビューして", "PRをレビュー", "PR見て", "コードレビュー", or when performing automated or manual code reviews on GitHub pull requests. Provides a structured, incremental review workflow with security checks, file prioritization, and merge readiness assessment.

Use this skill whenever the user wants to implement something using TDD (Test-Driven Development), mentions "Red Green Refactor", says "テスト駆動", "テスト書いて", "TDDで実装", "テストファースト", "test-driven", or asks to write a test for a function that doesn't exist yet. This skill enforces a strict type-first, stub-first discipline: types and stubs must exist before any test is written. Invoke this skill even if the user just says "TDDで" or "write a test for X" — the skill will handle the full Red → Green → Refactor cycle.

1 hook across 1 event