@yeongjaeyou/claude-code-config 0.4.0 → 0.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/ask-codex.md +131 -345
- package/.claude/commands/ask-deepwiki.md +15 -15
- package/.claude/commands/ask-gemini.md +134 -352
- package/.claude/commands/code-review.md +41 -40
- package/.claude/commands/commit-and-push.md +35 -36
- package/.claude/commands/council.md +318 -0
- package/.claude/commands/edit-notebook.md +34 -33
- package/.claude/commands/gh/create-issue-label.md +19 -17
- package/.claude/commands/gh/decompose-issue.md +66 -65
- package/.claude/commands/gh/init-project.md +46 -52
- package/.claude/commands/gh/post-merge.md +74 -79
- package/.claude/commands/gh/resolve-issue.md +38 -46
- package/.claude/commands/plan.md +15 -14
- package/.claude/commands/tm/convert-prd.md +53 -53
- package/.claude/commands/tm/post-merge.md +92 -112
- package/.claude/commands/tm/resolve-issue.md +148 -154
- package/.claude/commands/tm/review-prd-with-codex.md +272 -279
- package/.claude/commands/tm/sync-to-github.md +189 -212
- package/.claude/guidelines/cv-guidelines.md +30 -0
- package/.claude/guidelines/id-reference.md +34 -0
- package/.claude/guidelines/work-guidelines.md +17 -0
- package/.claude/skills/notion-md-uploader/SKILL.md +252 -0
- package/.claude/skills/notion-md-uploader/references/notion_block_types.md +323 -0
- package/.claude/skills/notion-md-uploader/references/setup_guide.md +156 -0
- package/.claude/skills/notion-md-uploader/scripts/__pycache__/markdown_parser.cpython-311.pyc +0 -0
- package/.claude/skills/notion-md-uploader/scripts/__pycache__/notion_client.cpython-311.pyc +0 -0
- package/.claude/skills/notion-md-uploader/scripts/__pycache__/notion_converter.cpython-311.pyc +0 -0
- package/.claude/skills/notion-md-uploader/scripts/markdown_parser.py +607 -0
- package/.claude/skills/notion-md-uploader/scripts/notion_client.py +337 -0
- package/.claude/skills/notion-md-uploader/scripts/notion_converter.py +477 -0
- package/.claude/skills/notion-md-uploader/scripts/upload_md.py +298 -0
- package/.claude/skills/skill-creator/LICENSE.txt +202 -0
- package/.claude/skills/skill-creator/SKILL.md +209 -0
- package/.claude/skills/skill-creator/scripts/init_skill.py +303 -0
- package/.claude/skills/skill-creator/scripts/package_skill.py +110 -0
- package/.claude/skills/skill-creator/scripts/quick_validate.py +65 -0
- package/package.json +1 -1
|
@@ -1,37 +1,37 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Convert Draft to TaskMaster PRD
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Convert a draft file to TaskMaster PRD format.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
**Template:** Copy `.claude/guideline/tm/prd-guide.md` to create draft
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
-
|
|
9
|
-
-
|
|
10
|
-
- `.taskmaster/templates/example_prd.txt`
|
|
7
|
+
**Principles:**
|
|
8
|
+
- Preserve original content (do not add or remove arbitrarily)
|
|
9
|
+
- Write in Korean
|
|
10
|
+
- Follow `.taskmaster/templates/example_prd.txt` format
|
|
11
11
|
|
|
12
12
|
---
|
|
13
13
|
|
|
14
|
-
##
|
|
14
|
+
## Arguments
|
|
15
15
|
|
|
16
|
-
|
|
17
|
-
-
|
|
18
|
-
-
|
|
16
|
+
Receive draft file path via `$ARGUMENTS`:
|
|
17
|
+
- Example: `/tm:convert-prd .taskmaster/docs/my-idea.md`
|
|
18
|
+
- If empty, request path input via AskUserQuestion
|
|
19
19
|
|
|
20
20
|
---
|
|
21
21
|
|
|
22
|
-
##
|
|
22
|
+
## Workflow
|
|
23
23
|
|
|
24
|
-
### 1.
|
|
24
|
+
### 1. Read Draft
|
|
25
25
|
|
|
26
26
|
```bash
|
|
27
27
|
cat $ARGUMENTS
|
|
28
28
|
```
|
|
29
29
|
|
|
30
|
-
|
|
30
|
+
If file does not exist or is empty, request content.
|
|
31
31
|
|
|
32
|
-
### 2.
|
|
32
|
+
### 2. Verify Target Format
|
|
33
33
|
|
|
34
|
-
`.taskmaster/templates/example_prd.txt`
|
|
34
|
+
`.taskmaster/templates/example_prd.txt` structure:
|
|
35
35
|
|
|
36
36
|
```
|
|
37
37
|
<context>
|
|
@@ -49,79 +49,79 @@ cat $ARGUMENTS
|
|
|
49
49
|
</PRD>
|
|
50
50
|
```
|
|
51
51
|
|
|
52
|
-
### 3.
|
|
52
|
+
### 3. Convert
|
|
53
53
|
|
|
54
|
-
|
|
54
|
+
Rearrange draft content to match the format above:
|
|
55
55
|
|
|
56
|
-
|
|
|
57
|
-
|
|
58
|
-
|
|
|
59
|
-
|
|
|
60
|
-
| (UX
|
|
61
|
-
|
|
|
62
|
-
|
|
|
63
|
-
|
|
|
64
|
-
|
|
|
56
|
+
| Draft Section | PRD Section |
|
|
57
|
+
|---------------|-------------|
|
|
58
|
+
| What to build | Overview |
|
|
59
|
+
| Key features | Core Features |
|
|
60
|
+
| (UX content) | User Experience |
|
|
61
|
+
| Tech stack | Technical Architecture |
|
|
62
|
+
| Build order | Development Roadmap, Logical Dependency Chain |
|
|
63
|
+
| Other (concerns) | Risks and Mitigations |
|
|
64
|
+
| Other (references) | Appendix |
|
|
65
65
|
|
|
66
|
-
|
|
67
|
-
-
|
|
68
|
-
-
|
|
69
|
-
-
|
|
70
|
-
- Development Roadmap
|
|
66
|
+
**Conversion Rules:**
|
|
67
|
+
- Do not add content not in original
|
|
68
|
+
- Mark empty sections as "[To be written]"
|
|
69
|
+
- Write in Korean
|
|
70
|
+
- Organize Development Roadmap by Phase
|
|
71
71
|
|
|
72
|
-
### 4.
|
|
72
|
+
### 4. Output Result
|
|
73
73
|
|
|
74
|
-
|
|
74
|
+
Output the complete converted PRD.
|
|
75
75
|
|
|
76
|
-
### 5.
|
|
76
|
+
### 5. Save
|
|
77
77
|
|
|
78
|
-
AskUserQuestion
|
|
79
|
-
-
|
|
80
|
-
-
|
|
78
|
+
Confirm via AskUserQuestion before saving:
|
|
79
|
+
- Default: `.taskmaster/docs/prd.md`
|
|
80
|
+
- Alternative paths allowed
|
|
81
81
|
|
|
82
|
-
### 6.
|
|
82
|
+
### 6. Next Steps
|
|
83
83
|
|
|
84
84
|
```
|
|
85
|
-
[
|
|
85
|
+
[Conversion Complete]
|
|
86
86
|
|
|
87
|
-
|
|
87
|
+
Next step:
|
|
88
88
|
task-master parse-prd .taskmaster/docs/prd.md
|
|
89
89
|
```
|
|
90
90
|
|
|
91
91
|
---
|
|
92
92
|
|
|
93
|
-
##
|
|
93
|
+
## Output Format
|
|
94
94
|
|
|
95
95
|
```markdown
|
|
96
96
|
<context>
|
|
97
97
|
# Overview
|
|
98
|
-
[
|
|
98
|
+
[What to build content]
|
|
99
99
|
|
|
100
100
|
# Core Features
|
|
101
|
-
[
|
|
101
|
+
[Key features content]
|
|
102
102
|
|
|
103
103
|
# User Experience
|
|
104
|
-
[UX
|
|
104
|
+
[UX content or to be written]
|
|
105
105
|
</context>
|
|
106
106
|
|
|
107
107
|
<PRD>
|
|
108
108
|
# Technical Architecture
|
|
109
|
-
[
|
|
109
|
+
[Tech stack content]
|
|
110
110
|
|
|
111
111
|
# Development Roadmap
|
|
112
|
-
## Phase 1: [
|
|
113
|
-
- [
|
|
112
|
+
## Phase 1: [Name]
|
|
113
|
+
- [Feature]
|
|
114
114
|
|
|
115
|
-
## Phase 2: [
|
|
116
|
-
- [
|
|
115
|
+
## Phase 2: [Name]
|
|
116
|
+
- [Feature]
|
|
117
117
|
|
|
118
118
|
# Logical Dependency Chain
|
|
119
|
-
[
|
|
119
|
+
[Build order based dependencies]
|
|
120
120
|
|
|
121
121
|
# Risks and Mitigations
|
|
122
|
-
[
|
|
122
|
+
[Concerns]
|
|
123
123
|
|
|
124
124
|
# Appendix
|
|
125
|
-
[
|
|
125
|
+
[References]
|
|
126
126
|
</PRD>
|
|
127
127
|
```
|
|
@@ -1,201 +1,181 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Post-Merge Cleanup (TaskMaster Integration)
|
|
2
2
|
|
|
3
|
-
PR
|
|
3
|
+
After PR merge, perform branch cleanup, TaskMaster status update, and CLAUDE.md update.
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
- **GitHub PR/Issue**: `#1`, `#2` (GitHub
|
|
7
|
-
- **TaskMaster Task**: `task 1`, `task 1.1` (tasks.json
|
|
5
|
+
**Important - ID Distinction:**
|
|
6
|
+
- **GitHub PR/Issue**: `#1`, `#2` (GitHub numbers)
|
|
7
|
+
- **TaskMaster Task**: `task 1`, `task 1.1` (based on tasks.json)
|
|
8
8
|
|
|
9
|
-
`@CLAUDE.md
|
|
9
|
+
Follow project guidelines in `@CLAUDE.md`.
|
|
10
10
|
|
|
11
11
|
---
|
|
12
12
|
|
|
13
|
-
##
|
|
13
|
+
## Arguments
|
|
14
14
|
|
|
15
|
-
- PR
|
|
15
|
+
- PR number (optional): If not provided, determine from conversation context or request selection from recent merged PR list
|
|
16
16
|
|
|
17
17
|
---
|
|
18
18
|
|
|
19
|
-
##
|
|
19
|
+
## Workflow
|
|
20
20
|
|
|
21
|
-
### 1. PR
|
|
21
|
+
### 1. Verify PR Information
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
|
-
#
|
|
25
|
-
#
|
|
24
|
+
# Use PR number if provided as argument
|
|
25
|
+
# Otherwise show recent merged PR list
|
|
26
26
|
gh pr list --state merged --limit 5
|
|
27
27
|
|
|
28
|
-
# PR
|
|
29
|
-
gh pr view <
|
|
28
|
+
# Get PR details
|
|
29
|
+
gh pr view <PR_NUMBER> --json number,title,baseRefName,headRefName,body,state
|
|
30
30
|
```
|
|
31
31
|
|
|
32
|
-
|
|
33
|
-
- `state
|
|
34
|
-
-
|
|
32
|
+
**Verify:**
|
|
33
|
+
- Check if `state` is `MERGED`
|
|
34
|
+
- Extract `Task Master reference: task N` from PR body
|
|
35
35
|
|
|
36
|
-
### 2. TaskMaster Task ID
|
|
36
|
+
### 2. Extract TaskMaster Task ID
|
|
37
37
|
|
|
38
|
-
|
|
38
|
+
Identify TaskMaster ID from PR body or linked Issue:
|
|
39
39
|
|
|
40
40
|
```bash
|
|
41
|
-
# PR
|
|
42
|
-
gh pr view <
|
|
41
|
+
# Extract from PR body
|
|
42
|
+
gh pr view <PR_NUMBER> --json body | grep -o "Task Master reference: task [0-9.]*"
|
|
43
43
|
|
|
44
|
-
#
|
|
45
|
-
gh pr view <
|
|
44
|
+
# Or extract from linked Issue
|
|
45
|
+
gh pr view <PR_NUMBER> --json closedIssues
|
|
46
46
|
```
|
|
47
47
|
|
|
48
|
-
|
|
48
|
+
**Example extraction result:**
|
|
49
49
|
```
|
|
50
|
-
Task Master
|
|
51
|
-
|
|
52
|
-
|
|
50
|
+
Task Master reference: task 1
|
|
51
|
+
-> TaskMaster Task ID: 1
|
|
52
|
+
-> Related Subtasks: 1.1, 1.2, 1.3 (if any)
|
|
53
53
|
```
|
|
54
54
|
|
|
55
|
-
### 3. TaskMaster
|
|
55
|
+
### 3. Update TaskMaster Status
|
|
56
56
|
|
|
57
57
|
```bash
|
|
58
|
-
#
|
|
58
|
+
# Check main task status
|
|
59
59
|
task-master show <TASK_ID>
|
|
60
60
|
|
|
61
|
-
#
|
|
62
|
-
#
|
|
61
|
+
# Verify all subtasks are done
|
|
62
|
+
# If subtasks exist and all are complete:
|
|
63
63
|
task-master set-status --id=<TASK_ID> --status=done
|
|
64
64
|
|
|
65
|
-
#
|
|
66
|
-
#
|
|
67
|
-
#
|
|
65
|
+
# If subtasks exist and only some are complete:
|
|
66
|
+
# -> Keep main task as in-progress
|
|
67
|
+
# -> Mark only completed subtasks as done
|
|
68
68
|
```
|
|
69
69
|
|
|
70
|
-
|
|
70
|
+
**Status Update Rules:**
|
|
71
71
|
|
|
72
|
-
|
|
|
73
|
-
|
|
74
|
-
| PR
|
|
75
|
-
| PR
|
|
76
|
-
| PR
|
|
72
|
+
| Situation | Main Task Status | Subtask Status |
|
|
73
|
+
|-----------|------------------|----------------|
|
|
74
|
+
| PR merged, no subtasks | done | N/A |
|
|
75
|
+
| PR merged, all subtasks complete | done | all done |
|
|
76
|
+
| PR merged, some subtasks remain | in-progress | only completed ones done |
|
|
77
77
|
|
|
78
|
-
### 4.
|
|
78
|
+
### 4. Check Local Changes
|
|
79
79
|
|
|
80
80
|
```bash
|
|
81
81
|
git status --porcelain
|
|
82
82
|
```
|
|
83
83
|
|
|
84
|
-
- **Untracked
|
|
85
|
-
- **Modified/Staged
|
|
86
|
-
- **
|
|
87
|
-
-
|
|
88
|
-
-
|
|
89
|
-
- **stash
|
|
90
|
-
- **pop**: `git stash pop` (
|
|
91
|
-
- **apply**: `git stash apply` (
|
|
92
|
-
-
|
|
84
|
+
- **Untracked files (`??`)**: Ignore and proceed (no impact on branch switch)
|
|
85
|
+
- **Modified/Staged files (`M`, `A`, `D`, etc.)**: Ask via AskUserQuestion for handling:
|
|
86
|
+
- **Stash and proceed**: `git stash push -m "post-merge: temp save"`
|
|
87
|
+
- **Discard changes**: `git checkout -- . && git clean -fd`
|
|
88
|
+
- **Abort**: User handles manually
|
|
89
|
+
- **If stash selected**: After completion, ask via AskUserQuestion about stash restore:
|
|
90
|
+
- **pop**: `git stash pop` (restore and remove stash)
|
|
91
|
+
- **apply**: `git stash apply` (restore and keep stash)
|
|
92
|
+
- **later**: User handles manually
|
|
93
93
|
|
|
94
|
-
### 5.
|
|
94
|
+
### 5. Switch to Base Branch
|
|
95
95
|
|
|
96
96
|
```bash
|
|
97
97
|
git fetch origin
|
|
98
|
-
git checkout <baseRefName> #
|
|
98
|
+
git checkout <baseRefName> # usually main
|
|
99
99
|
git pull origin <baseRefName>
|
|
100
100
|
```
|
|
101
101
|
|
|
102
|
-
### 6.
|
|
102
|
+
### 6. Clean Up Issue Branch (Optional)
|
|
103
103
|
|
|
104
|
-
AskUserQuestion
|
|
104
|
+
Ask via AskUserQuestion about local branch deletion:
|
|
105
105
|
|
|
106
106
|
```bash
|
|
107
|
-
#
|
|
108
|
-
git branch -d <headRefName> #
|
|
107
|
+
# If deletion desired
|
|
108
|
+
git branch -d <headRefName> # e.g., issue-1
|
|
109
109
|
```
|
|
110
110
|
|
|
111
|
-
### 7.
|
|
111
|
+
### 7. Check Next Task
|
|
112
112
|
|
|
113
113
|
```bash
|
|
114
|
-
#
|
|
114
|
+
# Check next available task in TaskMaster
|
|
115
115
|
task-master next
|
|
116
116
|
|
|
117
|
-
#
|
|
118
|
-
# Next task: Task 2 -
|
|
117
|
+
# Example output:
|
|
118
|
+
# Next task: Task 2 - Build design system and theme
|
|
119
119
|
# Dependencies satisfied: Task 1 (done)
|
|
120
120
|
```
|
|
121
121
|
|
|
122
|
-
### 8. CLAUDE.md
|
|
122
|
+
### 8. Analyze and Update CLAUDE.md
|
|
123
123
|
|
|
124
|
-
|
|
125
|
-
-
|
|
126
|
-
-
|
|
127
|
-
-
|
|
124
|
+
**Analysis targets:**
|
|
125
|
+
- Temporary instructions related to resolved Issue/Task (mentions of `#1`, `task 1`)
|
|
126
|
+
- Outdated or inaccurate information
|
|
127
|
+
- Newly discovered patterns/conventions
|
|
128
128
|
|
|
129
|
-
|
|
130
|
-
-
|
|
131
|
-
-
|
|
132
|
-
-
|
|
129
|
+
**Draft update proposal and confirm with user:**
|
|
130
|
+
- Delete: Temporary notes related to resolved issues
|
|
131
|
+
- Add: New patterns discovered during work
|
|
132
|
+
- Modify: Changed information
|
|
133
133
|
|
|
134
|
-
### 9.
|
|
134
|
+
### 9. Commit Changes (Optional)
|
|
135
135
|
|
|
136
|
-
CLAUDE.md
|
|
136
|
+
If CLAUDE.md was modified, ask via AskUserQuestion about committing:
|
|
137
137
|
|
|
138
138
|
```bash
|
|
139
139
|
git add CLAUDE.md
|
|
140
|
-
git commit -m "docs: CLAUDE.md
|
|
140
|
+
git commit -m "docs: update CLAUDE.md (reflecting task $TASK_ID completion)"
|
|
141
141
|
git push origin main
|
|
142
142
|
```
|
|
143
143
|
|
|
144
144
|
---
|
|
145
145
|
|
|
146
|
-
##
|
|
146
|
+
## Result Report
|
|
147
147
|
|
|
148
148
|
```
|
|
149
|
-
[
|
|
149
|
+
[Post-Merge Cleanup Complete]
|
|
150
150
|
|
|
151
|
-
PR
|
|
152
|
-
- PR: #<
|
|
153
|
-
-
|
|
154
|
-
-
|
|
151
|
+
PR Info:
|
|
152
|
+
- PR: #<PR_NUMBER>
|
|
153
|
+
- Title: <PR title>
|
|
154
|
+
- Branch: <headRefName> -> <baseRefName>
|
|
155
155
|
|
|
156
|
-
TaskMaster
|
|
156
|
+
TaskMaster Status:
|
|
157
157
|
- Task ID: task <N>
|
|
158
|
-
-
|
|
159
|
-
- Subtasks:
|
|
158
|
+
- Status: done
|
|
159
|
+
- Subtasks: all complete (1.1, 1.2, 1.3)
|
|
160
160
|
|
|
161
|
-
|
|
162
|
-
- [x]
|
|
163
|
-
- [x] TaskMaster
|
|
164
|
-
- [ ] CLAUDE.md
|
|
161
|
+
Cleanup:
|
|
162
|
+
- [x] Local branch deleted: issue-<N>
|
|
163
|
+
- [x] TaskMaster status updated
|
|
164
|
+
- [ ] CLAUDE.md updated (no changes)
|
|
165
165
|
|
|
166
|
-
|
|
167
|
-
- task-master next
|
|
168
|
-
- /tm:resolve-issue <M>
|
|
166
|
+
Next Steps:
|
|
167
|
+
- task-master next -> Task <M>
|
|
168
|
+
- Start with /tm:resolve-issue <M>
|
|
169
169
|
```
|
|
170
170
|
|
|
171
171
|
---
|
|
172
172
|
|
|
173
|
-
##
|
|
173
|
+
## Work Guidelines
|
|
174
174
|
|
|
175
|
-
|
|
176
|
-
- 코드나 문서 작성 시 이모지 사용 금지
|
|
177
|
-
- 불명확한 사항은 추측하지 말고 AskUserQuestion으로 질문
|
|
178
|
-
- CLAUDE.md 변경은 반드시 사용자 확인 후 진행
|
|
179
|
-
- TaskMaster 상태 변경, 브랜치 삭제 등 되돌리기 어려운 작업은 항상 사용자 확인 필요
|
|
180
|
-
- 커밋, PR, 이슈에 'Generated with Claude', 'Co-Authored-By: Claude' 등 Claude attribution 금지
|
|
175
|
+
> See [Work Guidelines](../guidelines/work-guidelines.md)
|
|
181
176
|
|
|
182
177
|
---
|
|
183
178
|
|
|
184
|
-
## ID
|
|
179
|
+
## ID Reference
|
|
185
180
|
|
|
186
|
-
|
|
187
|
-
[이 커맨드에서 사용되는 ID들]
|
|
188
|
-
|
|
189
|
-
GitHub:
|
|
190
|
-
- PR 번호: #13, #14
|
|
191
|
-
- Issue 번호: #1, #2 (PR과 동일 네임스페이스)
|
|
192
|
-
- 브랜치: issue-1, issue-2
|
|
193
|
-
|
|
194
|
-
TaskMaster:
|
|
195
|
-
- 메인 태스크: task 1, task 2
|
|
196
|
-
- Subtask: task 1.1, task 1.2
|
|
197
|
-
|
|
198
|
-
연결:
|
|
199
|
-
- PR 본문의 "Task Master 참조: task N"
|
|
200
|
-
- PR 본문의 "Closes #N" (GitHub Issue 연결)
|
|
201
|
-
```
|
|
181
|
+
> See [ID Reference](../guidelines/id-reference.md)
|