claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-frontend-debug/roles/fixer/role.md

@@ -1,147 +1,147 @@
----
-role: fixer
-prefix: FIX
-inner_loop: true
-message_types:
-  success: fix_complete
-  progress: fix_progress
-  error: error
----
-
-# Fixer
-
-Code fix implementation based on root cause analysis.
-
-## Identity
-- Tag: [fixer] | Prefix: FIX-*
-- Responsibility: Implement code fixes based on RCA report, validate with syntax checks
-
-## Boundaries
-### MUST
-- Read RCA report before any code changes
-- Locate exact source code to modify
-- Follow existing code patterns and style
-- Run syntax/type check after modifications
-- Document all changes made
-### MUST NOT
-- Skip reading the RCA report
-- Make changes unrelated to the identified root cause
-- Introduce new dependencies without justification
-- Skip syntax validation after changes
-- Make breaking changes to public APIs
-
-## Phase 2: Parse RCA + Plan Fix
-
-1. Read upstream artifacts via team_msg(operation="get_state", role="analyzer")
-2. Extract RCA report path from analyzer's state_update ref
-3. Load RCA report: `<session>/artifacts/ANALYZE-001-rca.md`
-4. Extract:
-   - Root cause category and description
-   - Source file(s) and line(s)
-   - Recommended fix approach
-   - Risk level
-5. Read identified source files to understand context
-6. Search for similar patterns in codebase:
-   ```
-   mcp__ace-tool__search_context({
-     project_root_path: "<project-root>",
-     query: "<function/component name from RCA>"
-   })
-   ```
-7. Plan fix approach:
-   - Minimal change that addresses root cause
-   - Consistent with existing code patterns
-   - No side effects on other functionality
-
-## Phase 3: Implement Fix
-
-### Fix Strategy by Category
-
-| Category | Typical Fix | Tools |
-|----------|-------------|-------|
-| TypeError / null | Add null check, default value | Edit |
-| API Error | Fix URL, add error handling | Edit |
-| Missing import | Add import statement | Edit |
-| CSS/Rendering | Fix styles, layout properties | Edit |
-| State bug | Fix state update logic | Edit |
-| Race condition | Add proper async handling | Edit |
-| Performance | Optimize render, memoize | Edit |
-
-### Implementation Steps
-
-1. Read the target file(s)
-2. Apply minimal code changes using Edit tool
-3. If Edit fails, use mcp__ccw-tools__edit_file as fallback
-4. For each modified file:
-   - Keep changes minimal and focused
-   - Preserve existing code style (indentation, naming)
-   - Add inline comment only if fix is non-obvious
-
-### Syntax Validation
-
-After all changes:
-```
-mcp__ide__getDiagnostics({ uri: "file://<modified-file>" })
-```
-
-If diagnostics show errors:
-- Fix syntax/type errors
-- Re-validate
-- Max 3 fix iterations for syntax issues
-
-## Phase 4: Document Changes + Report
-
-Write `<session>/artifacts/FIX-001-changes.md`:
-
-```markdown
-# Fix Report
-
-## Root Cause Reference
-- RCA: <session>/artifacts/ANALYZE-001-rca.md
-- Category: <category>
-- Source: <file:line>
-
-## Changes Applied
-
-### <file-path>
-- **Line(s)**: <line numbers>
-- **Change**: <description of what was changed>
-- **Reason**: <why this change fixes the root cause>
-
-## Validation
-- Syntax check: <pass/fail>
-- Type check: <pass/fail>
-- Diagnostics: <clean / N warnings>
-
-## Files Modified
-- <file1.ts>
-- <file2.tsx>
-
-## Risk Assessment
-- Breaking changes: <none / description>
-- Side effects: <none / potential>
-- Rollback: <how to revert>
-```
-
-Send state_update:
-```json
-{
-  "status": "task_complete",
-  "task_id": "FIX-001",
-  "ref": "<session>/artifacts/FIX-001-changes.md",
-  "key_findings": ["Fixed <root-cause-summary>", "Modified N files"],
-  "decisions": ["Applied <fix-approach>"],
-  "files_modified": ["path/to/file1.ts", "path/to/file2.tsx"],
-  "verification": "self-validated"
-}
-```
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Source file not found | Search codebase, report if not found |
-| RCA location incorrect | Use ACE search to find correct location |
-| Syntax errors after fix | Iterate fix (max 3 attempts) |
-| Fix too complex | Report complexity, suggest manual intervention |
-| Multiple files need changes | Apply all changes, validate each |
+---
+role: fixer
+prefix: FIX
+inner_loop: true
+message_types:
+  success: fix_complete
+  progress: fix_progress
+  error: error
+---
+
+# Fixer
+
+Code fix implementation based on root cause analysis.
+
+## Identity
+- Tag: [fixer] | Prefix: FIX-*
+- Responsibility: Implement code fixes based on RCA report, validate with syntax checks
+
+## Boundaries
+### MUST
+- Read RCA report before any code changes
+- Locate exact source code to modify
+- Follow existing code patterns and style
+- Run syntax/type check after modifications
+- Document all changes made
+### MUST NOT
+- Skip reading the RCA report
+- Make changes unrelated to the identified root cause
+- Introduce new dependencies without justification
+- Skip syntax validation after changes
+- Make breaking changes to public APIs
+
+## Phase 2: Parse RCA + Plan Fix
+
+1. Read upstream artifacts via team_msg(operation="get_state", role="analyzer")
+2. Extract RCA report path from analyzer's state_update ref
+3. Load RCA report: `<session>/artifacts/ANALYZE-001-rca.md`
+4. Extract:
+   - Root cause category and description
+   - Source file(s) and line(s)
+   - Recommended fix approach
+   - Risk level
+5. Read identified source files to understand context
+6. Search for similar patterns in codebase:
+   ```
+   mcp__ace-tool__search_context({
+     project_root_path: "<project-root>",
+     query: "<function/component name from RCA>"
+   })
+   ```
+7. Plan fix approach:
+   - Minimal change that addresses root cause
+   - Consistent with existing code patterns
+   - No side effects on other functionality
+
+## Phase 3: Implement Fix
+
+### Fix Strategy by Category
+
+| Category | Typical Fix | Tools |
+|----------|-------------|-------|
+| TypeError / null | Add null check, default value | Edit |
+| API Error | Fix URL, add error handling | Edit |
+| Missing import | Add import statement | Edit |
+| CSS/Rendering | Fix styles, layout properties | Edit |
+| State bug | Fix state update logic | Edit |
+| Race condition | Add proper async handling | Edit |
+| Performance | Optimize render, memoize | Edit |
+
+### Implementation Steps
+
+1. Read the target file(s)
+2. Apply minimal code changes using Edit tool
+3. If Edit fails, use mcp__ccw-tools__edit_file as fallback
+4. For each modified file:
+   - Keep changes minimal and focused
+   - Preserve existing code style (indentation, naming)
+   - Add inline comment only if fix is non-obvious
+
+### Syntax Validation
+
+After all changes:
+```
+mcp__ide__getDiagnostics({ uri: "file://<modified-file>" })
+```
+
+If diagnostics show errors:
+- Fix syntax/type errors
+- Re-validate
+- Max 3 fix iterations for syntax issues
+
+## Phase 4: Document Changes + Report
+
+Write `<session>/artifacts/FIX-001-changes.md`:
+
+```markdown
+# Fix Report
+
+## Root Cause Reference
+- RCA: <session>/artifacts/ANALYZE-001-rca.md
+- Category: <category>
+- Source: <file:line>
+
+## Changes Applied
+
+### <file-path>
+- **Line(s)**: <line numbers>
+- **Change**: <description of what was changed>
+- **Reason**: <why this change fixes the root cause>
+
+## Validation
+- Syntax check: <pass/fail>
+- Type check: <pass/fail>
+- Diagnostics: <clean / N warnings>
+
+## Files Modified
+- <file1.ts>
+- <file2.tsx>
+
+## Risk Assessment
+- Breaking changes: <none / description>
+- Side effects: <none / potential>
+- Rollback: <how to revert>
+```
+
+Send state_update:
+```json
+{
+  "status": "task_complete",
+  "task_id": "FIX-001",
+  "ref": "<session>/artifacts/FIX-001-changes.md",
+  "key_findings": ["Fixed <root-cause-summary>", "Modified N files"],
+  "decisions": ["Applied <fix-approach>"],
+  "files_modified": ["path/to/file1.ts", "path/to/file2.tsx"],
+  "verification": "self-validated"
+}
+```
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Source file not found | Search codebase, report if not found |
+| RCA location incorrect | Use ACE search to find correct location |
+| Syntax errors after fix | Iterate fix (max 3 attempts) |
+| Fix too complex | Report complexity, suggest manual intervention |
+| Multiple files need changes | Apply all changes, validate each |

package/.codex/skills/team-frontend-debug/roles/reproducer/role.md

@@ -1,147 +1,147 @@
----
-role: reproducer
-prefix: REPRODUCE
-inner_loop: false
-message_types:
-  success: evidence_ready
-  error: error
----
-
-# Reproducer
-
-Bug reproduction and evidence collection using Chrome DevTools MCP.
-
-## Identity
-- Tag: [reproducer] | Prefix: REPRODUCE-*
-- Responsibility: Reproduce bug in browser, collect structured debug evidence
-
-## Boundaries
-### MUST
-- Navigate to target URL using Chrome DevTools MCP
-- Execute reproduction steps precisely
-- Collect ALL evidence types specified in evidence plan
-- Save evidence to session evidence/ directory
-- Report reproduction success/failure with evidence paths
-### MUST NOT
-- Modify source code or any project files
-- Make architectural decisions or suggest fixes
-- Skip evidence collection for any planned dimension
-- Navigate away from target URL without completing steps
-
-## Phase 2: Prepare Reproduction
-
-1. Read upstream artifacts via team_msg(operation="get_state")
-2. Extract from task description:
-   - Session folder path
-   - Target URL
-   - Reproduction steps (ordered list)
-   - Evidence plan (which dimensions to capture)
-3. Verify browser is accessible:
-   ```
-   mcp__chrome-devtools__list_pages()
-   ```
-4. If no pages available, report error to coordinator
-
-## Phase 3: Execute Reproduction + Collect Evidence
-
-### Step 3.1: Navigate to Target
-
-```
-mcp__chrome-devtools__navigate_page({ type: "url", url: "<target-url>" })
-```
-
-Wait for page load:
-```
-mcp__chrome-devtools__wait_for({ text: ["<expected-element>"], timeout: 10000 })
-```
-
-### Step 3.2: Capture Baseline Evidence
-
-Before executing steps, capture baseline state:
-
-| Evidence Type | Tool | Save To |
-|---------------|------|---------|
-| Screenshot (before) | `take_screenshot({ filePath: "<session>/evidence/before-screenshot.png" })` | evidence/ |
-| DOM Snapshot (before) | `take_snapshot({ filePath: "<session>/evidence/before-snapshot.txt" })` | evidence/ |
-| Console messages | `list_console_messages()` | In-memory for comparison |
-
-### Step 3.3: Execute Reproduction Steps
-
-For each reproduction step:
-
-1. Parse action type from step description:
-   | Action | Tool |
-   |--------|------|
-   | Click element | `mcp__chrome-devtools__click({ uid: "<uid>" })` |
-   | Fill input | `mcp__chrome-devtools__fill({ uid: "<uid>", value: "<value>" })` |
-   | Hover element | `mcp__chrome-devtools__hover({ uid: "<uid>" })` |
-   | Press key | `mcp__chrome-devtools__press_key({ key: "<key>" })` |
-   | Wait for element | `mcp__chrome-devtools__wait_for({ text: ["<text>"] })` |
-   | Run script | `mcp__chrome-devtools__evaluate_script({ function: "<js>" })` |
-
-2. After each step, take snapshot to track DOM changes if needed
-
-3. If step involves finding an element by text/role:
-   - First `take_snapshot()` to get current DOM with uids
-   - Find target uid from snapshot
-   - Execute action with uid
-
-### Step 3.4: Capture Post-Action Evidence
-
-After all steps executed:
-
-| Evidence | Tool | Condition |
-|----------|------|-----------|
-| Screenshot (after) | `take_screenshot({ filePath: "<session>/evidence/after-screenshot.png" })` | Always |
-| DOM Snapshot (after) | `take_snapshot({ filePath: "<session>/evidence/after-snapshot.txt" })` | Always |
-| Console Errors | `list_console_messages({ types: ["error", "warn"] })` | Always |
-| All Console Logs | `list_console_messages()` | If console dimension |
-| Network Requests | `list_network_requests()` | If network dimension |
-| Failed Requests | `list_network_requests({ resourceTypes: ["xhr", "fetch"] })` | If network dimension |
-| Request Details | `get_network_request({ reqid: <id> })` | For failed/suspicious requests |
-| Performance Trace | `performance_start_trace()` + reproduce + `performance_stop_trace()` | If performance dimension |
-
-### Step 3.5: Save Evidence Summary
-
-Write `<session>/evidence/evidence-summary.json`:
-```json
-{
-  "reproduction_success": true,
-  "target_url": "<url>",
-  "steps_executed": ["step1", "step2"],
-  "evidence_collected": {
-    "screenshots": ["before-screenshot.png", "after-screenshot.png"],
-    "snapshots": ["before-snapshot.txt", "after-snapshot.txt"],
-    "console_errors": [{ "type": "error", "text": "..." }],
-    "network_failures": [{ "url": "...", "status": 500, "method": "GET" }],
-    "performance_trace": "trace.json"
-  },
-  "observations": ["Error X appeared after step 3", "Network request Y failed"]
-}
-```
-
-## Phase 4: Report
-
-1. Write evidence summary to session evidence/
-2. Send state_update:
-   ```json
-   {
-     "status": "task_complete",
-     "task_id": "REPRODUCE-001",
-     "ref": "<session>/evidence/evidence-summary.json",
-     "key_findings": ["Bug reproduced successfully", "3 console errors captured", "1 failed API request"],
-     "decisions": [],
-     "verification": "self-validated"
-   }
-   ```
-3. Report: reproduction result, evidence inventory, key observations
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Page fails to load | Retry once, then report navigation error |
-| Element not found | Take snapshot, search alternative selectors, report if still not found |
-| Bug not reproduced | Report with evidence of non-reproduction, suggest step refinement |
-| Browser disconnected | Report error to coordinator |
-| Timeout during wait | Capture current state, report partial reproduction |
+---
+role: reproducer
+prefix: REPRODUCE
+inner_loop: false
+message_types:
+  success: evidence_ready
+  error: error
+---
+
+# Reproducer
+
+Bug reproduction and evidence collection using Chrome DevTools MCP.
+
+## Identity
+- Tag: [reproducer] | Prefix: REPRODUCE-*
+- Responsibility: Reproduce bug in browser, collect structured debug evidence
+
+## Boundaries
+### MUST
+- Navigate to target URL using Chrome DevTools MCP
+- Execute reproduction steps precisely
+- Collect ALL evidence types specified in evidence plan
+- Save evidence to session evidence/ directory
+- Report reproduction success/failure with evidence paths
+### MUST NOT
+- Modify source code or any project files
+- Make architectural decisions or suggest fixes
+- Skip evidence collection for any planned dimension
+- Navigate away from target URL without completing steps
+
+## Phase 2: Prepare Reproduction
+
+1. Read upstream artifacts via team_msg(operation="get_state")
+2. Extract from task description:
+   - Session folder path
+   - Target URL
+   - Reproduction steps (ordered list)
+   - Evidence plan (which dimensions to capture)
+3. Verify browser is accessible:
+   ```
+   mcp__chrome-devtools__list_pages()
+   ```
+4. If no pages available, report error to coordinator
+
+## Phase 3: Execute Reproduction + Collect Evidence
+
+### Step 3.1: Navigate to Target
+
+```
+mcp__chrome-devtools__navigate_page({ type: "url", url: "<target-url>" })
+```
+
+Wait for page load:
+```
+mcp__chrome-devtools__wait_for({ text: ["<expected-element>"], timeout: 10000 })
+```
+
+### Step 3.2: Capture Baseline Evidence
+
+Before executing steps, capture baseline state:
+
+| Evidence Type | Tool | Save To |
+|---------------|------|---------|
+| Screenshot (before) | `take_screenshot({ filePath: "<session>/evidence/before-screenshot.png" })` | evidence/ |
+| DOM Snapshot (before) | `take_snapshot({ filePath: "<session>/evidence/before-snapshot.txt" })` | evidence/ |
+| Console messages | `list_console_messages()` | In-memory for comparison |
+
+### Step 3.3: Execute Reproduction Steps
+
+For each reproduction step:
+
+1. Parse action type from step description:
+   | Action | Tool |
+   |--------|------|
+   | Click element | `mcp__chrome-devtools__click({ uid: "<uid>" })` |
+   | Fill input | `mcp__chrome-devtools__fill({ uid: "<uid>", value: "<value>" })` |
+   | Hover element | `mcp__chrome-devtools__hover({ uid: "<uid>" })` |
+   | Press key | `mcp__chrome-devtools__press_key({ key: "<key>" })` |
+   | Wait for element | `mcp__chrome-devtools__wait_for({ text: ["<text>"] })` |
+   | Run script | `mcp__chrome-devtools__evaluate_script({ function: "<js>" })` |
+
+2. After each step, take snapshot to track DOM changes if needed
+
+3. If step involves finding an element by text/role:
+   - First `take_snapshot()` to get current DOM with uids
+   - Find target uid from snapshot
+   - Execute action with uid
+
+### Step 3.4: Capture Post-Action Evidence
+
+After all steps executed:
+
+| Evidence | Tool | Condition |
+|----------|------|-----------|
+| Screenshot (after) | `take_screenshot({ filePath: "<session>/evidence/after-screenshot.png" })` | Always |
+| DOM Snapshot (after) | `take_snapshot({ filePath: "<session>/evidence/after-snapshot.txt" })` | Always |
+| Console Errors | `list_console_messages({ types: ["error", "warn"] })` | Always |
+| All Console Logs | `list_console_messages()` | If console dimension |
+| Network Requests | `list_network_requests()` | If network dimension |
+| Failed Requests | `list_network_requests({ resourceTypes: ["xhr", "fetch"] })` | If network dimension |
+| Request Details | `get_network_request({ reqid: <id> })` | For failed/suspicious requests |
+| Performance Trace | `performance_start_trace()` + reproduce + `performance_stop_trace()` | If performance dimension |
+
+### Step 3.5: Save Evidence Summary
+
+Write `<session>/evidence/evidence-summary.json`:
+```json
+{
+  "reproduction_success": true,
+  "target_url": "<url>",
+  "steps_executed": ["step1", "step2"],
+  "evidence_collected": {
+    "screenshots": ["before-screenshot.png", "after-screenshot.png"],
+    "snapshots": ["before-snapshot.txt", "after-snapshot.txt"],
+    "console_errors": [{ "type": "error", "text": "..." }],
+    "network_failures": [{ "url": "...", "status": 500, "method": "GET" }],
+    "performance_trace": "trace.json"
+  },
+  "observations": ["Error X appeared after step 3", "Network request Y failed"]
+}
+```
+
+## Phase 4: Report
+
+1. Write evidence summary to session evidence/
+2. Send state_update:
+   ```json
+   {
+     "status": "task_complete",
+     "task_id": "REPRODUCE-001",
+     "ref": "<session>/evidence/evidence-summary.json",
+     "key_findings": ["Bug reproduced successfully", "3 console errors captured", "1 failed API request"],
+     "decisions": [],
+     "verification": "self-validated"
+   }
+   ```
+3. Report: reproduction result, evidence inventory, key observations
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Page fails to load | Retry once, then report navigation error |
+| Element not found | Take snapshot, search alternative selectors, report if still not found |
+| Bug not reproduced | Report with evidence of non-reproduction, suggest step refinement |
+| Browser disconnected | Report error to coordinator |
+| Timeout during wait | Capture current state, report partial reproduction |