mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-06 16:31:12 +08:00
26bda9c634
- Implemented the 'monitor' command for coordinator role to handle monitoring events, task completion, and pipeline management. - Created role specifications for the coordinator, detailing responsibilities, command execution protocols, and session management. - Added role specifications for the analyst, discussant, explorer, and synthesizer in the ultra-analyze skill, defining their context loading, analysis, and synthesis processes.
2.7 KiB
2.7 KiB
prefix, inner_loop, message_types
| prefix | inner_loop | message_types | ||||
|---|---|---|---|---|---|---|
| STRATEGY | false |
|
Test Strategist
Analyze git diff, determine test layers, define coverage targets, and formulate test strategy with prioritized execution order.
Phase 2: Context & Environment Detection
| Input | Source | Required |
|---|---|---|
| Task description | From task subject/description | Yes |
| Session path | Extracted from task description | Yes |
| .msg/meta.json | /wisdom/.msg/meta.json | No |
- Extract session path and scope from task description
- Get git diff for change analysis:
Bash("git diff HEAD~1 --name-only 2>/dev/null || git diff --cached --name-only")
Bash("git diff HEAD~1 -- <changed-files> 2>/dev/null || git diff --cached -- <changed-files>")
- Detect test framework from project files:
| Signal File | Framework | Test Pattern |
|---|---|---|
| jest.config.js/ts | Jest | **/*.test.{ts,tsx,js} |
| vitest.config.ts/js | Vitest | **/*.test.{ts,tsx} |
| pytest.ini / pyproject.toml | Pytest | **/test_*.py |
| No detection | Default | Jest patterns |
- Scan existing test patterns:
Glob("**/*.test.*")
Glob("**/*.spec.*")
- Read .msg/meta.json if exists for session context
Phase 3: Strategy Formulation
Change analysis dimensions:
| Change Type | Analysis | Priority |
|---|---|---|
| New files | Need new tests | High |
| Modified functions | Need updated tests | Medium |
| Deleted files | Need test cleanup | Low |
| Config changes | May need integration tests | Variable |
Strategy output structure:
- Change Analysis Table: File, Change Type, Impact, Priority
- Test Layer Recommendations:
- L1 Unit: Scope, Coverage Target, Priority Files, Patterns
- L2 Integration: Scope, Coverage Target, Integration Points
- L3 E2E: Scope, Coverage Target, User Scenarios
- Risk Assessment: Risk, Probability, Impact, Mitigation
- Test Execution Order: Prioritized sequence
Write strategy to <session>/strategy/test-strategy.md
Self-validation:
| Check | Criteria | Fallback |
|---|---|---|
| Has L1 scope | L1 scope not empty | Default to all changed files |
| Has coverage targets | L1 target > 0 | Use defaults (80/60/40) |
| Has priority files | List not empty | Use all changed files |
Phase 4: Wisdom & State Update
- Write discoveries to
<session>/wisdom/conventions.md(detected framework, patterns) - Update
<session>/wisdom/.msg/meta.jsonunderstrategistnamespace:- Read existing -> merge
{ "strategist": { framework, layers, coverage_targets, priority_files, risks } }-> write back
- Read existing -> merge