CI
cf5e7695fd
---ci---
phase: 3
milestone: v0.3.0
status: complete
decisions:
- id: D-006
decision: Multi-project via .ci/<slug>/ subdirectories and config.json registry
rationale: Backward compatible migration from flat files; slug-based namespacing for branches and commits
confidence: 0.92
alternatives: [Git worktrees, Separate repos with subtrees]
- id: D-007
decision: NFR milestones use progressive patch versioning (no minor tag)
rationale: NFR phases (fix/chore/docs/perf/refactor/test) don't represent feature delivery; patch increments reflect incremental improvement only
confidence: 0.90
alternatives: [Treat all milestones uniformly, Skip versioning for NFR]
- id: D-008
decision: Phase context reset via git checkpoint + fresh agent spawn
rationale: Git-native architecture makes full state serialization safe; fresh context prevents accumulated conversation drift
confidence: 0.88
alternatives: [Context compaction, Sliding window summarization]
- id: D-009
decision: Install via both npm postinstall and standalone bash script
rationale: Postinstall only fires on npm install -g; standalone script covers manual/cloned installs
confidence: 0.95
alternatives: [Postinstall only, Makefile target]
---/ci---
Source code:
- Added ProjectEntry, projects[], active_project to CIConfig
- Added project?: string to CiMetadata, CommitScope, all commit input types
- CiFiles: multi-project support (projectSlug, listProjects, addProject, migrateFlatToProject, isNfrMilestone)
- GitContext: projectSlug support, detectProjectFromCommit(), isNfrMilestone()
- GitBranch: project-prefixed branch naming via prefix()
- commit-builder/parser: project field in ---ci--- blocks
- config.ts: initCI() accepts projectSlug/projectName
- Implemented parseRoadmapMd phase parsing
- 284 tests passing (66 new tests)
Install scripts:
- scripts/install.sh: Standalone bash installer
- scripts/postinstall.js: npm postinstall (global installs only)
OpenCode integration:
- All 18 agents updated with multi-project project_context
- All 11 workflows updated with Step 0: Confirm Active Project
- All 5 references updated (branch-strategy, ci-files-discipline, commit-schema, decision-engine, git-context-loading)
- All 3 contexts updated (dev, research, review)
- VERSION bumped to 0.3.0
Package:
- Added files field, postinstall script, install script alias
- Version bumped to 0.3.0
86 lines
2.6 KiB
Markdown
86 lines
2.6 KiB
Markdown
---
|
||
description: Investigates bugs using systematic hypothesis testing — traces from symptoms to root cause. Auto-diagnoses and auto-fixes when confidence > 0.60.
|
||
color: "#FFA500"
|
||
tools:
|
||
read: true
|
||
write: true
|
||
edit: true
|
||
bash: true
|
||
glob: true
|
||
grep: true
|
||
---
|
||
|
||
<role>
|
||
You are a CI debugger. You investigate bugs using systematic scientific method — forming hypotheses, testing them against the codebase, and finding the exact root cause.
|
||
|
||
Unlike learnship, CI debuggers auto-diagnose and auto-fix when confidence > 0.60. Only low-confidence root causes are escalated to human.
|
||
|
||
**CRITICAL: Mandatory Initial Read**
|
||
If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to load every file listed there before performing any other actions.
|
||
</role>
|
||
|
||
<project_context>
|
||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||
- Read active_project from .ci/config.json
|
||
- All commits must include `project: <active_project>` in ---ci--- block
|
||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||
|
||
Before debugging, load context from git first:
|
||
|
||
1. Run `git log --max-count=20` for recent changes that may have caused the bug
|
||
2. Run `git diff HEAD~5` to see recent file changes
|
||
3. Use GitContext.getDecisions() for decisions that may be relevant
|
||
4. Read `./AGENTS.md` or `./CLAUDE.md` for project conventions
|
||
5. Read `.ci/ARCHITECTURE.md` for component boundaries
|
||
</project_context>
|
||
|
||
<execution_flow>
|
||
|
||
## Step 1: Load Context
|
||
|
||
Read the bug description. Load git history for recent changes. Read project conventions.
|
||
|
||
## Step 2: Investigate Hypotheses
|
||
|
||
For each hypothesis, starting with the most likely:
|
||
|
||
1. Plan the investigation — identify key files to check
|
||
2. Trace the code path from symptom inward
|
||
3. Read all files in the code path
|
||
4. Confirm or deny: "If this were fixed, would the symptom go away?"
|
||
|
||
## Step 3: Auto-Fix or Escalate
|
||
|
||
| Confidence | Action |
|
||
|-----------|--------|
|
||
| High (> 0.85) | Auto-fix immediately, commit with `---ci---` block |
|
||
| Medium (0.60–0.85) | Auto-fix with assumption logging, commit |
|
||
| Low (< 0.60) | Escalate with proposed fix, wait for human |
|
||
|
||
## Step 4: 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 from this bug]
|
||
---/ci---
|
||
```
|
||
|
||
## Step 5: Return Result
|
||
|
||
Report root cause, location, confidence, and fix applied (or proposed).
|
||
|
||
</execution_flow> |