feat(P02): opencode integration layer (#2)

18 CI agents, 11 workflows, 11 commands, 5 references, 3 contexts. Zero learnship dependencies.
This commit was merged in pull request #2.
This commit is contained in:
2026-05-29 13:27:29 +00:00
parent eedcdd4282
commit 2f738c33b7
50 changed files with 3113 additions and 0 deletions
+78
View File
@@ -0,0 +1,78 @@
---
description: Systematic CI debugging with git context — triage, diagnose root cause, auto-fix or escalate
---
# CI Debug
Systematic debugging workflow: triage → root cause diagnosis → auto-fix or escalate. Uses git history to find recent changes that may have caused the bug.
**Usage:** `ci-debug [description]`
## Step 1: Load Git Context
```bash
git log --max-count=20
git diff HEAD~5
git branch -a
```
Load recent changes to identify potential causes.
## Step 2: Triage
If no description provided, ask: "What is the exact symptom?"
Gather:
- Symptom description
- Expected behavior
- When it started (check git log for recent changes)
- What has been tried
## Step 3: Hypothesis Testing
For each hypothesis (most likely first):
1. Identify key files to check
2. Trace the code path from symptom to root
3. Read all files in the path
4. Confirm or deny: "If this were fixed, would the symptom go away?"
## Step 4: Auto-Fix or Escalate
Based on confidence:
| Confidence | Action |
|-----------|--------|
| High (> 0.85) | Auto-fix, commit with `---ci---` block |
| Medium (0.600.85) | Auto-fix with assumption logging, commit |
| Low (< 0.60) | Escalate with proposed fix |
## Step 5: Commit Fix
```
fix(P##): [root cause description]
---ci---
phase: [N]
milestone: [vX.X]
status: execute
decisions:
- id: D-XXX
decision: [fix approach]
rationale: [evidence]
confidence: 0.XX
alternatives: []
lessons:
- [lesson learned]
---/ci---
```
## Step 6: Verify Fix
Run relevant tests to confirm the fix works:
```bash
npm test
npm run typecheck
```
Report: root cause, location, confidence, fix applied.