maxwell2732/claudecode-research-harness-workflow/ci

CI failure reported
    ↓
┌─────────────────────────────────────────┐
│       Test vs. Implementation           │
├─────────────────────────────────────────┤
│  Analyze the cause:                     │
│  ├── Implementation is wrong → Fix impl │
│  ├── Test is outdated → Confirm w/ user │
│  └── Environment issue → Fix env        │
└─────────────────────────────────────────┘

⚠️ Prohibited actions when CI fails
 
The following "solutions" are prohibited:
 
| Prohibited | Example | Correct approach |
|------------|---------|------------------|
| Skipping tests | `it.skip(...)` | Fix the implementation |
| Removing assertions | Delete `expect()` | Verify expected values |
| Bypassing CI checks | `continue-on-error` | Fix the root cause |
| Relaxing lint rules | `eslint-disable` | Fix the code |

🔴 CI is failing
 
**A decision is needed**:
 
1.**Implementation is wrong** → Fix the implementation ✅
2.**Test expected value is outdated** → Ask user for confirmation
3.**Environment issue** → Fix the environment configuration
 
⚠️ Tampering with tests (skipping, removing assertions) is prohibited
 
Which applies here?

## 🚨 Approval Request for Test/Config Change
 
### Reason
[Why this change is necessary]
 
### Change Content
[Diff]
 
### Alternatives Considered
-[ ] Confirmed that fixing the implementation cannot resolve this
 
Waiting for explicit user approval

# Analyze commits with structured format
git log --format="%h|%s|%an|%ad" --date=short -10
 
# Analyze chronologically with topological order
git log --topo-order --oneline -20
 
# Link changed files to causes
git log --raw --oneline -5

🔍 CI Failure Cause Analysis
 
Recent commits (structured):
| Hash | Subject | Author | Date |
|------|---------|--------|------|
| a1b2c3d | feat: update API | Alice | 2026-02-04 |
| e4f5g6h | test: add tests | Bob | 2026-02-03 |
 
Changed files (--raw):
├── src/api/endpoint.ts (Modified) ← type error here
├── tests/api.test.ts (Modified)
└── package.json (Modified)
 
→ Commit a1b2c3d is likely the cause
  Type error: src/api/endpoint.ts:42

Task tool:
  subagent_type="ci-cd-fixer"
  prompt="Please diagnose and fix the CI failure. Error log: {error_log}"

🔧 How to talk about broken CI
 
1.**"CI failed" / "It went red"**
   -Automated tests are failing
 
2.**"Why is it failing?"**
   -Investigate the cause
 
3.**"Fix it"**
   -Attempt automatic repair
 
💡 Important: Fixes that "cheat" tests are prohibited
   -❌ Deleting or skipping tests
   -✅ Properly fixing the code
 
If you think "the test seems wrong",
confirm first before deciding on a course of action