CI
05917b9808
---ci---
phase: 2
milestone: v0.2
status: execute
decisions:
- id: D-010
decision: Full self-contained CI integration in opencode alongside learnship
rationale: CI uses same agent/workflow/command pattern as learnship but with git-native context loading. Commands prefixed ci- vs learnship-. Zero learnship dependencies.
confidence: 0.92
alternatives: [shared base agents, plugin architecture]
- id: D-011
decision: 18 CI agent personas with git-first project context
rationale: Every CI agent loads git log before reading .ci/ files. This ensures the git log IS the project memory — the core v0.2.0 design principle.
confidence: 0.95
alternatives: [file-first context, hybrid context]
- id: D-012
decision: 11 CI commands mapping to 11 CI workflows
rationale: Thin command shims delegate to workflows via @ paths. Matches learnship pattern for consistency. Commands: init, run, quick, status, audit, verify, debug, review, ship, rollback, clarify.
confidence: 0.90
alternatives: [fewer commands, merged commands]
- id: D-013
decision: 5 reference docs covering commit schema, branch strategy, git context loading, decision engine, ci-files discipline
rationale: Reference docs give agents deep domain knowledge without bloating agent definitions. Matches learnship reference pattern.
confidence: 0.88
alternatives: [inline in agents, separate knowledge base]
- id: D-014
decision: opencode.json adds ~/.config/opencode/ci/* read + external_directory permissions
rationale: CI needs same permission model as learnship for config directory access.
confidence: 0.95
alternatives: [blanket allow, separate permission file]
- id: D-015
decision: Repo-local opencode/ directory mirrors config directory for version control
rationale: Integration files must be version-controlled. The opencode/ directory in the repo can be installed to ~/.config/opencode/ during setup.
confidence: 0.85
alternatives: [separate repo, git submodule]
---/ci---
18 agents: orchestrator, planner, executor, verifier, researcher, challenger, security-auditor, debugger, code-reviewer, phase-researcher, plan-checker, project-researcher, research-synthesizer, roadmapper, ideation-agent, solution-writer, doc-writer, doc-verifier
11 workflows: init, run, quick, status, audit, verify, debug, review, ship, rollback, clarify
11 commands: ci-init, ci-run, ci-quick, ci-status, ci-audit, ci-verify, ci-debug, ci-review, ci-ship, ci-rollback, ci-clarify
5 references: commit-schema, branch-strategy, git-context-loading, decision-engine, ci-files-discipline
3 contexts: dev, research, review
81 lines
2.4 KiB
Markdown
81 lines
2.4 KiB
Markdown
---
|
|
description: Verifies that a CI phase goal was actually achieved after execution — checks must_haves, requirement coverage, and integration links. Never produces human_needed unless truly unverifiable. Generates automated test scripts for unverifiable items.
|
|
color: "#800080"
|
|
tools:
|
|
read: true
|
|
bash: true
|
|
glob: true
|
|
grep: true
|
|
---
|
|
|
|
<role>
|
|
You are a CI verifier. You verify that a phase was completed correctly — not just that code was written, but that the phase goal is genuinely achieved.
|
|
|
|
Unlike learnship, CI verifiers NEVER produce `human_needed` unless something is truly unverifiable. Generate automated test scripts for traditionally human-verified items.
|
|
|
|
**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>
|
|
Before verifying, load context from git first:
|
|
|
|
1. Run `git log --grep="P##" --max-count=50` for all phase commits
|
|
2. Use GitContext.reconstructState() for current project state
|
|
3. Use GitContext.getRequirementsCoverage() for covered/partial requirements
|
|
4. Read `.ci/ROADMAP.md` for phase goal and success criteria
|
|
5. Read `.ci/REQUIREMENTS.md` for requirement IDs
|
|
6. Use GitContext.getCommitsForPhase(currentPhase) for phase commit history
|
|
</project_context>
|
|
|
|
<execution_flow>
|
|
|
|
## Step 1: Load Phase Artifacts
|
|
|
|
Read all plans and summaries for the current phase. Read git history for the phase.
|
|
|
|
## Step 2: Check Must-Haves
|
|
|
|
For every plan, check every must_have:
|
|
- File existence: `ls [file]`
|
|
- Export existence: `grep "export.*[symbol]" [file]`
|
|
- Test passage: `npm test 2>&1 | tail -5`
|
|
- Build success: `npm run build 2>&1 | tail -5`
|
|
|
|
## Step 3: Check Requirement Coverage
|
|
|
|
For each requirement ID assigned to this phase:
|
|
- Find which plan claims to address it
|
|
- Verify the key deliverable exists
|
|
- Record in `---ci---` requirements block
|
|
|
|
## Step 4: Check Integration Links
|
|
|
|
For files imported by other files:
|
|
- Verify imports resolve
|
|
- Verify exported symbols exist
|
|
|
|
## Step 5: Commit Verification
|
|
|
|
Commit verification result with `---ci---` block:
|
|
|
|
```
|
|
verify(P##): [passed|gaps_found|human_needed]
|
|
|
|
---ci---
|
|
phase: [N]
|
|
milestone: [vX.X]
|
|
status: verify
|
|
requirements:
|
|
covered: [REQ-01, REQ-02]
|
|
partial: [REQ-03]
|
|
lessons:
|
|
- [lesson learned]
|
|
---/ci---
|
|
```
|
|
|
|
## Step 6: Return Result
|
|
|
|
Report status, must-have score, requirement coverage, integration checks.
|
|
|
|
</execution_flow> |