@yeongjaeyou/claude-code-config 0.11.1 → 0.12.0

package/.claude/commands/gh/decompose-issue.md

@@ -9,16 +9,23 @@ Break down large work items into manageable, independent issues. Follow project
    - Scan `.claude/agents/` for custom agents (read YAML frontmatter)
    - Scan `.claude/skills/` for available skills (read SKILL.md)
    - Check `.mcp.json` for configured MCP servers
-3. Analyze work: Understand core requirements and objectives
-4. Decompose work: Split major tasks into smaller, manageable sub-tasks or issues. **Aim for optimal count over excessive issues (keep it manageable)**
-5. Analyze dependencies: Identify prerequisite tasks
-6. Suggest milestone name: Propose a milestone to group decomposed tasks
-7. Check related PRs (optional): Run `gh pr list --state closed --limit 20` for similar work references (skip if none)
-8. Output decomposed issues: Display issues with proposed milestone name
-9. Ask about GitHub creation: Use AskUserQuestion to let user decide on milestone and issue creation
-   - Create milestone: `gh api repos/:owner/:repo/milestones -f title="Milestone Name" -f description="Description"`
-   - Assign issues with `--milestone` option
-10. **Add issues to GitHub Project (optional)**
+   - Detect test frameworks (jest.config.*, pytest.ini, vitest.config.*, pyproject.toml, etc.)
+3. **Check TDD applicability** (if user hasn't specified):
+   - Analyze work type: code implementation vs docs/infra/config
+   - If test framework detected + code work → Ask: "TDD 기반으로 이슈 생성하시겠어요?"
+   - If no test framework → Inform: "TDD 반영이 필요없습니다. (이유: 테스트 프레임워크 미감지)"
+   - If non-code work (docs/infra) → Inform: "TDD 반영이 필요없습니다. (이유: 비코드 작업)"
+   - If TDD selected: Add `<!-- TDD: enabled -->` marker to each issue body
+4. Analyze work: Understand core requirements and objectives
+5. Decompose work: Split major tasks into smaller, manageable sub-tasks or issues. **Aim for optimal count over excessive issues (keep it manageable)**
+6. Analyze dependencies: Identify prerequisite tasks
+7. Suggest milestone name: Propose a milestone to group decomposed tasks
+8. Check related PRs (optional): Run `gh pr list --state closed --limit 20` for similar work references (skip if none)
+9. Output decomposed issues: Display issues with proposed milestone name
+10. Ask about GitHub creation: Use AskUserQuestion to let user decide on milestone and issue creation
+    - Create milestone: `gh api repos/:owner/:repo/milestones -f title="Milestone Name" -f description="Description"`
+    - Assign issues with `--milestone` option
+11. **Add issues to GitHub Project (optional)**
    - Check for existing projects: `gh project list --owner <owner> --format json`
    - If no project exists: Display "No project found. You can create one with `/gh:init-project`" and skip
    - If project exists: Ask user via AskUserQuestion whether to add issues
@@ -46,6 +53,8 @@ Examples (vary by project, for reference only):
 - **Priority**: `priority: high`, `priority: medium`, `priority: low`
 
 ### Description
+<!-- TDD: enabled --> ← Add this marker if TDD was selected in Step 3
+
 **Purpose**: [Why this is needed]
 
 **Tasks**:

package/.claude/commands/gh/resolve-issue.md

@@ -7,6 +7,7 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
 
 1. **Analyze Issue**:
    - Run `gh issue view $ISSUE_NUMBER --json title,body,comments,milestone` to get issue title, body, labels, and milestone
+   - **Check TDD marker**: Look for `<!-- TDD: enabled -->` in issue body → Set TDD workflow flag
    - If milestone exists, run `gh issue list --milestone "<milestone-name>" --json number,title,state` to view related issues and understand overall context
    - Identify requirements precisely
 
@@ -48,9 +49,16 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
 6. **Plan Resolution**: Based on analysis results, develop a concrete resolution plan and define work steps.
 
 7. **Resolve Issue**: Spawn sub-agents to modify code and implement features according to the plan.
+   - **If TDD enabled** (marker detected in Step 1):
+     1. 🔴 RED: Write failing tests first based on requirements
+     2. 🟢 GREEN: Implement minimal code to pass tests
+     3. 🔵 REFACTOR: Clean up while keeping tests green
+   - **If TDD not enabled**: Implement features directly according to the plan
    - **Execution verification required**: For Python scripts, executables, or any runnable code, always execute to verify correct behavior. Do not rely solely on file existence or previous results.
 
-8. **Write Tests**: Spawn independent sub-agents per file to write unit tests in parallel, achieving at least 80% coverage.
+8. **Write Tests**:
+   - **If TDD enabled**: Verify test coverage meets target (tests already written in Step 7), add missing edge cases if needed
+   - **If TDD not enabled**: Spawn independent sub-agents per file to write unit tests in parallel, achieving at least 80% coverage
 
 9. **Validate**: Run tests, lint checks, and build verification in parallel using independent sub-agents to validate code quality.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeongjaeyou/claude-code-config",
-  "version": "0.11.1",
+  "version": "0.12.0",
   "description": "Claude Code CLI custom commands, agents, and skills",
   "bin": {
     "claude-code-config": "./bin/cli.js"