@wbern/claude-instructions 2.9.0 → 2.9.1

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/README.md CHANGED
@@ -78,7 +78,7 @@ Then add a postinstall script to your `package.json`:
78
78
  "postinstall": "claude-instructions --scope=project --overwrite"
79
79
  },
80
80
  "devDependencies": {
81
- "@wbern/claude-instructions": "^2.9.0"
81
+ "@wbern/claude-instructions": "^2.9.1"
82
82
  }
83
83
  }
84
84
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wbern/claude-instructions",
3
- "version": "2.9.0",
3
+ "version": "2.9.1",
4
4
  "description": "TDD workflow commands for Claude Code CLI",
5
5
  "type": "module",
6
6
  "bin": "./bin/cli.js",
@@ -17,7 +17,11 @@ _order: 99
17
17
 
18
18
  Create a new custom command in `src/sources/` following the patterns below. Assess the structure carefully using the below info but also researching the repo.
19
19
 
20
- Command to create: $ARGUMENTS
20
+ **User arguments:**
21
+
22
+ Contribute-a-command: $ARGUMENTS
23
+
24
+ **End of user arguments**
21
25
 
22
26
  ## File Structure
23
27
 
@@ -49,9 +53,13 @@ Optional: `_requested-tools` (array), `_selectedByDefault: false`
49
53
  ### Test-Driven Development (spike, red, green, refactor, cycle)
50
54
 
51
55
  ```markdown
52
- [PHASE] PHASE! Apply the below to the info given by user input here:
56
+ **User arguments:**
57
+
58
+ [CommandName]: [DOLLAR]ARGUMENTS
53
59
 
54
- [DOLLAR]ARGUMENTS
60
+ **End of user arguments**
61
+
62
+ [PHASE] PHASE! Apply the below to the user input above.
55
63
 
56
64
  < !-- docs INCLUDE path='src/fragments/universal-guidelines.md' -->
57
65
  < !-- /docs -->
@@ -80,7 +88,13 @@ Add for red: `aaa-pattern.md`
80
88
  < !-- docs INCLUDE path='src/fragments/beads-awareness.md' featureFlag='beads' -->
81
89
  < !-- /docs -->
82
90
 
83
- [Description and [DOLLAR] embedded in flow]
91
+ [Description]
92
+
93
+ **User arguments:**
94
+
95
+ [CommandName]: [DOLLAR]ARGUMENTS
96
+
97
+ **End of user arguments**
84
98
 
85
99
  < !-- docs INCLUDE path='src/fragments/discovery-phase.md' -->
86
100
  < !-- /docs -->
@@ -100,7 +114,11 @@ Add for red: `aaa-pattern.md`
100
114
 
101
115
  [Workflow description]
102
116
 
103
- [DOLLAR]
117
+ **User arguments:**
118
+
119
+ [CommandName]: [DOLLAR]ARGUMENTS
120
+
121
+ **End of user arguments**
104
122
 
105
123
  [Process steps]
106
124
  ```
@@ -43,8 +43,12 @@ argument-hint: [required-arg] [optional-arg]
43
43
 
44
44
  Your command instructions here.
45
45
 
46
+ **User arguments:**
47
+
46
48
  Add-command: $ARGUMENTS
47
49
 
50
+ **End of user arguments**
51
+
48
52
  File reference: @path/to/file.js
49
53
 
50
54
  Bash command output: (exclamation)git status(backticks)
@@ -47,8 +47,12 @@ Current branch status:
47
47
  Recent commits:
48
48
  !`git log --oneline -5`
49
49
 
50
+ **User arguments:**
51
+
50
52
  Ask: $ARGUMENTS
51
53
 
54
+ **End of user arguments**
55
+
52
56
  **This is the traditional Pull Request workflow**, but with explicit intent that review and approval are required.
53
57
 
54
58
  **Process:**
@@ -21,8 +21,12 @@ Execute the user's requested task (e.g., posting PR comments, GitHub issue comme
21
21
 
22
22
  ## Instructions
23
23
 
24
+ **User arguments:**
25
+
24
26
  Beepboop: $ARGUMENTS
25
27
 
28
+ **End of user arguments**
29
+
26
30
  **IMPORTANT Communication Format:**
27
31
 
28
32
  1. **Opening**: Begin with "*Beep boop, I am Claude Code 🤖, my user has reviewed and approved the following written by me:*"
@@ -17,8 +17,12 @@ _order: 2
17
17
 
18
18
  Create multiple atomic git commits, committing the smallest possible logical unit at a time
19
19
 
20
+ **User arguments:**
21
+
20
22
  Busycommit: $ARGUMENTS
21
23
 
24
+ **End of user arguments**
25
+
22
26
  <!-- docs INCLUDE path='src/fragments/commit-process.md' -->
23
27
  <!-- /docs -->
24
28
 
@@ -239,4 +239,8 @@ Provide a ready-to-paste PR description:
239
239
 
240
240
  ---
241
241
 
242
- Review target (branch name, PR number, or PR URL - leave empty for current branch): $ARGUMENTS
242
+ **User arguments:**
243
+
244
+ Code-review: $ARGUMENTS
245
+
246
+ **End of user arguments**
@@ -17,7 +17,11 @@ _order: 1
17
17
 
18
18
  Create a git commit following project standards
19
19
 
20
+ **User arguments:**
21
+
20
22
  Commit: $ARGUMENTS
21
23
 
24
+ **End of user arguments**
25
+
22
26
  <!-- docs INCLUDE path='src/fragments/commit-process.md' -->
23
27
  <!-- /docs -->
@@ -16,8 +16,12 @@ _order: 25
16
16
 
17
17
  Scan the Node.js repository and report what commit automation is in place.
18
18
 
19
+ **User arguments:**
20
+
19
21
  Commitlint-checklist: $ARGUMENTS
20
22
 
23
+ **End of user arguments**
24
+
21
25
  ## Checks to Scan
22
26
 
23
27
  Scan the repository for these configurations (do not display this list to user):
@@ -19,8 +19,12 @@ Create structured implementation plan that bridges product thinking (PRD) with t
19
19
  <!-- docs INCLUDE path='src/fragments/no-plan-files.md' featureFlag='no-plan-files' -->
20
20
  <!-- /docs -->
21
21
 
22
+ **User arguments:**
23
+
22
24
  Create-issues: $ARGUMENTS
23
25
 
26
+ **End of user arguments**
27
+
24
28
  (If no input provided, check conversation context<!-- docs INCLUDE path='src/fragments/create-issues-beads-context-hint.md' featureFlag='beads' -->
25
29
  <!-- /docs -->)
26
30
 
@@ -6,9 +6,13 @@ _category: Test-Driven Development
6
6
  _order: 5
7
7
  ---
8
8
 
9
+ **User arguments:**
10
+
9
11
  Cycle: $ARGUMENTS
10
12
 
11
- RED+GREEN+REFACTOR (one cycle) PHASE! Apply the below to the info given by user input.
13
+ **End of user arguments**
14
+
15
+ RED+GREEN+REFACTOR (one cycle) PHASE! Apply the below to the user input above.
12
16
 
13
17
  <!-- docs INCLUDE path='src/fragments/universal-guidelines.md' -->
14
18
  <!-- /docs -->
@@ -12,7 +12,11 @@ _order: 20
12
12
  <!-- docs INCLUDE path='src/fragments/beads-awareness.md' featureFlag='beads' -->
13
13
  <!-- /docs -->
14
14
 
15
- # Forever Mode: $ARGUMENTS
15
+ **User arguments:**
16
+
17
+ Forever: $ARGUMENTS
18
+
19
+ **End of user arguments**
16
20
 
17
21
  Run autonomously, finding and completing work until interrupted or truly stuck.
18
22
 
@@ -37,4 +37,8 @@ Present findings as a prioritized list with:
37
37
 
38
38
  If there are no gaps, confirm that everything discussed has been addressed.
39
39
 
40
+ **User arguments:**
41
+
40
42
  Gap: $ARGUMENTS
43
+
44
+ **End of user arguments**
@@ -6,9 +6,13 @@ _category: Test-Driven Development
6
6
  _order: 3
7
7
  ---
8
8
 
9
+ **User arguments:**
10
+
9
11
  Green: $ARGUMENTS
10
12
 
11
- GREEN PHASE! Apply the below to the info given by user input.
13
+ **End of user arguments**
14
+
15
+ GREEN PHASE! Apply the below to the user input above.
12
16
 
13
17
  <!-- docs INCLUDE path='src/fragments/universal-guidelines.md' -->
14
18
  <!-- /docs -->
@@ -21,8 +21,12 @@ Process:
21
21
 
22
22
  1. Get Issue Number
23
23
 
24
+ **User arguments:**
25
+
24
26
  Issue: $ARGUMENTS
25
27
 
28
+ **End of user arguments**
29
+
26
30
  - Check if argument is an issue number
27
31
  - Otherwise try branch name patterns: issue-123, 123-feature, feature/123, fix/123
28
32
  - If not found: ask user
@@ -25,8 +25,12 @@ Generate a complete TDD practice setup:
25
25
  <!-- docs INCLUDE path='src/fragments/no-plan-files.md' featureFlag='no-plan-files' -->
26
26
  <!-- /docs -->
27
27
 
28
+ **User arguments:**
29
+
28
30
  Kata: $ARGUMENTS
29
31
 
32
+ **End of user arguments**
33
+
30
34
  (This command is interactive - arguments are ignored)
31
35
 
32
36
  ## Data Source
@@ -161,4 +161,8 @@ Additional cross-cutting checks:
161
161
 
162
162
  ---
163
163
 
164
+ **User arguments:**
165
+
164
166
  Polish: $ARGUMENTS
167
+
168
+ **End of user arguments**
package/src/sources/pr.md CHANGED
@@ -27,8 +27,12 @@ Current branch status:
27
27
  Recent commits:
28
28
  !`git log --oneline -5`
29
29
 
30
+ **User arguments:**
31
+
30
32
  PR: $ARGUMENTS
31
33
 
34
+ **End of user arguments**
35
+
32
36
  **Process:**
33
37
 
34
38
  1. **Ensure Branch is Ready**:
@@ -6,9 +6,13 @@ _category: Test-Driven Development
6
6
  _order: 2
7
7
  ---
8
8
 
9
+ **User arguments:**
10
+
9
11
  Red: $ARGUMENTS
10
12
 
11
- RED PHASE! Apply the below to the info given by user input.
13
+ **End of user arguments**
14
+
15
+ RED PHASE! Apply the below to the user input above.
12
16
 
13
17
  <!-- docs INCLUDE path='src/fragments/universal-guidelines.md' -->
14
18
  <!-- /docs -->
@@ -6,9 +6,13 @@ _category: Test-Driven Development
6
6
  _order: 4
7
7
  ---
8
8
 
9
+ **User arguments:**
10
+
9
11
  Refactor: $ARGUMENTS
10
12
 
11
- Apply this document (specifically the Refactor phase) to the info given by user input.
13
+ **End of user arguments**
14
+
15
+ Apply this document (specifically the Refactor phase) to the user input above.
12
16
 
13
17
  <!-- docs INCLUDE path='src/fragments/universal-guidelines.md' -->
14
18
  <!-- /docs -->
@@ -12,7 +12,11 @@ _order: 20
12
12
  <!-- docs INCLUDE path='src/fragments/beads-awareness.md' featureFlag='beads' -->
13
13
  <!-- /docs -->
14
14
 
15
- # Research: $ARGUMENTS
15
+ **User arguments:**
16
+
17
+ Research: $ARGUMENTS
18
+
19
+ **End of user arguments**
16
20
 
17
21
  Research the following problem or question thoroughly, like a senior developer would.
18
22
 
@@ -45,8 +45,12 @@ Current branch status:
45
45
  Recent commits:
46
46
  !`git log --oneline -5`
47
47
 
48
+ **User arguments:**
49
+
48
50
  Ship: $ARGUMENTS
49
51
 
52
+ **End of user arguments**
53
+
50
54
  **Process:**
51
55
 
52
56
  1. **Verify Change Size**: Check git diff to ensure changes are small and focused
@@ -44,8 +44,12 @@ Current branch status:
44
44
  Recent commits:
45
45
  !`git log --oneline -5`
46
46
 
47
+ **User arguments:**
48
+
47
49
  Show: $ARGUMENTS
48
50
 
51
+ **End of user arguments**
52
+
49
53
  **Process:**
50
54
 
51
55
  1. **Verify Quality**: Check that changes meet show criteria
@@ -12,7 +12,11 @@ _order: 16
12
12
  <!-- docs INCLUDE path='src/fragments/beads-awareness.md' featureFlag='beads' -->
13
13
  <!-- /docs -->
14
14
 
15
- # Simplify: $ARGUMENTS
15
+ **User arguments:**
16
+
17
+ Simplify: $ARGUMENTS
18
+
19
+ **End of user arguments**
16
20
 
17
21
  <!-- docs INCLUDE path='src/fragments/fallback-arguments.md' -->
18
22
  <!-- /docs -->
@@ -6,9 +6,13 @@ _category: Test-Driven Development
6
6
  _order: 1
7
7
  ---
8
8
 
9
+ **User arguments:**
10
+
9
11
  Spike: $ARGUMENTS
10
12
 
11
- SPIKE PHASE! Apply the below to the info given by user input.
13
+ **End of user arguments**
14
+
15
+ SPIKE PHASE! Apply the below to the user input above.
12
16
 
13
17
  <!-- docs INCLUDE path='src/fragments/universal-guidelines.md' -->
14
18
  <!-- /docs -->
@@ -17,8 +17,12 @@ _order: 10
17
17
 
18
18
  Create a concise summary of the current conversation suitable for transferring context to a new conversation.
19
19
 
20
+ **User arguments:**
21
+
20
22
  Summarize: $ARGUMENTS
21
23
 
24
+ **End of user arguments**
25
+
22
26
  <!-- docs INCLUDE path='src/fragments/summarize-structure.md' -->
23
27
  <!-- /docs -->
24
28
 
@@ -77,4 +77,8 @@ Output a structured report:
77
77
 
78
78
  ---
79
79
 
80
- Test path (leave empty for all tests): $ARGUMENTS
80
+ **User arguments:**
81
+
82
+ TDD-review: $ARGUMENTS
83
+
84
+ **End of user arguments**
@@ -22,6 +22,10 @@ _order: 1
22
22
 
23
23
  ## Continue Conversation
24
24
 
25
+ **User arguments:**
26
+
25
27
  TDD: $ARGUMENTS
26
28
 
27
- Please continue with the above response, applying TDD approach.
29
+ **End of user arguments**
30
+
31
+ Please continue with the user input above, applying TDD approach.
@@ -179,4 +179,8 @@ This will:
179
179
 
180
180
  ---
181
181
 
182
+ **User arguments:**
183
+
182
184
  Upgrade: $ARGUMENTS
185
+
186
+ **End of user arguments**
@@ -17,7 +17,11 @@ _order: 1
17
17
  <!-- docs INCLUDE path='src/fragments/no-plan-files.md' featureFlag='no-plan-files' -->
18
18
  <!-- /docs -->
19
19
 
20
- Create a new git worktree for branch: $ARGUMENTS
20
+ **User arguments:**
21
+
22
+ Worktree-add: $ARGUMENTS
23
+
24
+ **End of user arguments**
21
25
 
22
26
  <current_state>
23
27
  Current branch: `git branch --show-current`
@@ -19,8 +19,12 @@ _order: 2
19
19
 
20
20
  Clean up merged worktrees by finding the oldest merged branch, consolidating settings, and removing stale worktrees.
21
21
 
22
+ **User arguments:**
23
+
22
24
  Worktree-cleanup: $ARGUMENTS
23
25
 
26
+ **End of user arguments**
27
+
24
28
  <current_state>
25
29
  Current branch: `git branch --show-current`
26
30
  Current worktrees: `git worktree list`