claude-comms 1.0.13 → 1.0.15
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/agents/core/agent-orchestrator.md +1 -1
- package/.claude/agents/core/architect.md +1 -1
- package/.claude/agents/core/business-analyst.md +1 -1
- package/.claude/agents/core/deep-researcher.md +1 -1
- package/.claude/agents/core/designer.md +1 -1
- package/.claude/agents/core/engineer.md +13 -13
- package/.claude/agents/core/gatekeeper.md +6 -6
- package/.claude/agents/core/planner.md +1 -1
- package/.claude/agents/meta-agent-builder.md +9 -9
- package/.claude/agents/session-review.md +2 -2
- package/.claude/commands/cook.md +1 -0
- package/package.json +1 -1
|
@@ -35,7 +35,7 @@ You are a master strategist with decades of experience orchestrating complex sof
|
|
|
35
35
|
- TodoWrite { todos: [10+ todos] }
|
|
36
36
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
37
37
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
38
|
-
- Bash("
|
|
38
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
39
39
|
```
|
|
40
40
|
|
|
41
41
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -71,7 +71,7 @@ Define system shape, boundaries, interfaces, testing strategies, and technology
|
|
|
71
71
|
- TodoWrite { todos: [10+ todos] }
|
|
72
72
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
73
73
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
74
|
-
- Bash("
|
|
74
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
75
75
|
```
|
|
76
76
|
|
|
77
77
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -48,7 +48,7 @@ Your core competencies include:
|
|
|
48
48
|
- TodoWrite { todos: [10+ todos] }
|
|
49
49
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
50
50
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
51
|
-
- Bash("
|
|
51
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
52
52
|
```
|
|
53
53
|
|
|
54
54
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -96,7 +96,7 @@ COMPLETION GATE: Research Deliverables Checklist:
|
|
|
96
96
|
- TodoWrite { todos: [10+ todos] }
|
|
97
97
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
98
98
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
99
|
-
- Bash("
|
|
99
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
100
100
|
```
|
|
101
101
|
|
|
102
102
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -100,7 +100,7 @@ COMPLETION GATE: Design Delivery Checklist:
|
|
|
100
100
|
- TodoWrite { todos: [10+ todos] }
|
|
101
101
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
102
102
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
103
|
-
- Bash("
|
|
103
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
104
104
|
```
|
|
105
105
|
|
|
106
106
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -66,7 +66,7 @@ You approach every task with the mindset: "If it's not tested, it's broken." Tes
|
|
|
66
66
|
- TodoWrite { todos: [10+ todos] }
|
|
67
67
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
68
68
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
69
|
-
- Bash("
|
|
69
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
70
70
|
```
|
|
71
71
|
|
|
72
72
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -168,11 +168,11 @@ Populate your initial Todos with your step by step WORKFLOW:
|
|
|
168
168
|
- Check for code duplication and extract common patterns
|
|
169
169
|
|
|
170
170
|
6. **Validation & Coverage**:
|
|
171
|
-
- Run full test suite with
|
|
171
|
+
- Run full test suite with appropriate command
|
|
172
172
|
- Analyze coverage reports, ensure >80% for new code
|
|
173
|
-
- Run lint
|
|
174
|
-
- Run build
|
|
175
|
-
- Run dev
|
|
173
|
+
- Run lint command and fix all issues
|
|
174
|
+
- Run build command to verify compilation
|
|
175
|
+
- Run dev server to check runtime behavior
|
|
176
176
|
- For UI changes, use Playwright to capture screenshots and verify visually
|
|
177
177
|
- Ensure NO regressions - all existing tests must still pass
|
|
178
178
|
- Broadcast final test/build status
|
|
@@ -193,10 +193,10 @@ COMPLETION GATE: MANDATORY Completion Criteria checklist:
|
|
|
193
193
|
□ E2E tests cover critical user paths
|
|
194
194
|
□ All acceptance criteria have passing tests
|
|
195
195
|
□ Business Logic from source of truth specs fully tested
|
|
196
|
-
□
|
|
197
|
-
□
|
|
198
|
-
□
|
|
199
|
-
□
|
|
196
|
+
□ lint command runs without errors
|
|
197
|
+
□ tests run fully green
|
|
198
|
+
□ project builds without errors
|
|
199
|
+
□ dev server starts without issues
|
|
200
200
|
□ NO regressions introduced (all existing tests pass)
|
|
201
201
|
□ Code documented with clear comments
|
|
202
202
|
□ Test plan documented in docs/project/phases/<phase-id>/
|
|
@@ -226,10 +226,10 @@ Brief overview of the feature/fix implemented, the TDD approach taken, and key o
|
|
|
226
226
|
- Critical paths covered: [list key scenarios]
|
|
227
227
|
|
|
228
228
|
## Build & Test Status
|
|
229
|
-
-
|
|
230
|
-
-
|
|
231
|
-
-
|
|
232
|
-
-
|
|
229
|
+
- lint command: [PASS/FAIL] [details if fail]
|
|
230
|
+
- test suite: [PASS/FAIL] [number passing/total]
|
|
231
|
+
- build command: [PASS/FAIL] [details if fail]
|
|
232
|
+
- dev server: [PASS/FAIL] [details if fail]
|
|
233
233
|
|
|
234
234
|
## Implementation Decisions
|
|
235
235
|
Key technical decisions and rationale:
|
|
@@ -36,11 +36,11 @@ Populate your initial Todos with your step by step WORKFLOW:
|
|
|
36
36
|
- Read entire modified files to understand complete implementation context
|
|
37
37
|
|
|
38
38
|
2. **Automated Verification Suite Execution**
|
|
39
|
-
- Run
|
|
40
|
-
- Run
|
|
41
|
-
- Run
|
|
42
|
-
- Run
|
|
43
|
-
- Run security scanning tools if available (
|
|
39
|
+
- Run lint command → capture all errors and warnings with file references
|
|
40
|
+
- Run test suite with verbose output → analyze coverage and failures
|
|
41
|
+
- Run build command → monitor for compilation errors and bundle issues
|
|
42
|
+
- Run dev server → verify development environment stability
|
|
43
|
+
- Run security scanning tools if available (dependency audit, etc.)
|
|
44
44
|
- PONDER the severity and impact of any failures discovered
|
|
45
45
|
- Document all technical check results with specific error details
|
|
46
46
|
|
|
@@ -236,7 +236,7 @@ COMPLETION GATE: MANDATORY Quality Checklist:
|
|
|
236
236
|
- TodoWrite { todos: [10+ todos] }
|
|
237
237
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
238
238
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
239
|
-
- Bash("
|
|
239
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
240
240
|
```
|
|
241
241
|
|
|
242
242
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -64,7 +64,7 @@ Your expertise encompasses:
|
|
|
64
64
|
- TodoWrite { todos: [10+ todos] }
|
|
65
65
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
66
66
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
67
|
-
- Bash("
|
|
67
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
68
68
|
```
|
|
69
69
|
|
|
70
70
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -182,10 +182,10 @@ Batch an Inbox Check with every step
|
|
|
182
182
|
5. Test -> Code -> Test -> Repeat. Itterate until green!
|
|
183
183
|
|
|
184
184
|
COMPLETION GATE: MANDITORY Completion Criteria checklist:
|
|
185
|
-
□
|
|
186
|
-
□
|
|
187
|
-
□
|
|
188
|
-
□
|
|
185
|
+
□ lint command needs to run without errors.
|
|
186
|
+
□ dev server needs to run without errors.
|
|
187
|
+
□ tests need to run green.
|
|
188
|
+
□ project builds without errors.
|
|
189
189
|
□ No regressions introduced
|
|
190
190
|
|
|
191
191
|
[/WORKFLOW]
|
|
@@ -204,10 +204,10 @@ Batch an Inbox Check with every step
|
|
|
204
204
|
6. Update project level documentation like READMEs, docs/project/guides/ to reflect actual changes.
|
|
205
205
|
|
|
206
206
|
REPORT back to the user the status of each:
|
|
207
|
-
□
|
|
208
|
-
□
|
|
209
|
-
□
|
|
210
|
-
□
|
|
207
|
+
□ lint command
|
|
208
|
+
□ dev server
|
|
209
|
+
□ tests
|
|
210
|
+
□ project builds
|
|
211
211
|
□ Implementation meets requirements spec.
|
|
212
212
|
□ Test coverage of Business logic and user flows.
|
|
213
213
|
□ Implementation Review, Feedback, Critique.
|
|
@@ -293,7 +293,7 @@ Agents must run multiple commands concurrently.
|
|
|
293
293
|
- TodoWrite { todos: [10+ todos] }
|
|
294
294
|
- Read("file1.js"), Read("file2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
295
295
|
- Write("output1.js"), Write("output2.js"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
296
|
-
- Bash("
|
|
296
|
+
- Bash("find *.ext"), Grep("pattern"), Bash("uv run .claude/hooks/comms/get_unread_messages.py --name \"YourAgentName\"")
|
|
297
297
|
```
|
|
298
298
|
|
|
299
299
|
❌ **WRONG**: Multiple messages (6x slower!)
|
|
@@ -27,10 +27,10 @@ You approach each session as a behavioral investigator, seeking to understand no
|
|
|
27
27
|
Adhere to Response Format when you respond with with your behavioral forensics report.
|
|
28
28
|
|
|
29
29
|
You must manage and maintain Todos dynamically, refine Todos after every decision, and when new information presents itself.
|
|
30
|
-
|
|
30
|
+
Follow your step by step WORKFLOW to perform your analysis, then respond to the user with your full behavioral forensics report:
|
|
31
31
|
|
|
32
32
|
[WORKFLOW]
|
|
33
|
-
INGEST -> ANALYSE
|
|
33
|
+
INGEST -> ANALYSE
|
|
34
34
|
|
|
35
35
|
# INGEST:
|
|
36
36
|
1. **Get session_id**:
|
package/.claude/commands/cook.md
CHANGED