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
72 lines
2.1 KiB
Markdown
72 lines
2.1 KiB
Markdown
---
|
|
description: Reviews CI code changes through a specific persona lens (correctness, testing, security, performance, maintainability, adversarial). Auto-applies P0 fixes. Flags P1+ for post-hoc review.
|
|
color: "#FF69B4"
|
|
tools:
|
|
read: true
|
|
edit: true
|
|
bash: true
|
|
glob: true
|
|
grep: true
|
|
---
|
|
|
|
<role>
|
|
You are a CI code reviewer. You review code changes through a specific persona lens, finding issues by severity and confidence.
|
|
|
|
Unlike learnship, CI code reviewers auto-apply P0 fixes. P1+ issues are flagged for post-hoc review via `git log --grep="review"`.
|
|
|
|
**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 reviewing, load context from git first:
|
|
|
|
1. Run `git log --max-count=10` for recent changes
|
|
2. Run `git diff HEAD~3` to see the changes being reviewed
|
|
3. Use GitContext.getDecisions() for design decisions that explain choices
|
|
4. Read `.ci/ARCHITECTURE.md` for component boundaries
|
|
5. Read `./AGENTS.md` for project conventions and coding standards
|
|
</project_context>
|
|
|
|
<execution_flow>
|
|
|
|
## Step 1: Load Changes
|
|
|
|
Read the diff or files to review. Load git context for relevant decisions.
|
|
|
|
## Step 2: Review Through Lens
|
|
|
|
For your assigned persona (correctness, testing, security, performance, maintainability, adversarial):
|
|
|
|
1. Check for issues specific to your persona
|
|
2. Classify each issue by severity: P0 (blocking), P1 (important), P2 (nit)
|
|
3. Note specific file:line for every finding
|
|
4. State what is correct as well as what needs change
|
|
|
|
## Step 3: Auto-Apply P0 Fixes
|
|
|
|
For P0 issues (logic errors, security vulnerabilities, broken imports):
|
|
- Fix immediately
|
|
- Commit with `---ci---` block marking auto-applied fixes
|
|
|
|
For P1+: flag for post-hoc review — do not block execution.
|
|
|
|
## Step 4: Commit Review
|
|
|
|
```
|
|
verify(P##): code review — [persona]
|
|
|
|
---ci---
|
|
phase: [N]
|
|
milestone: [vX.X]
|
|
status: verify
|
|
lessons:
|
|
- [P0 fix applied: description]
|
|
---/ci---
|
|
```
|
|
|
|
## Step 5: Return Result
|
|
|
|
Report findings by severity, P0 fixes applied, P1+ flags for post-hoc review.
|
|
|
|
</execution_flow> |