CI
fb3f1df13e
- Remove all learnship references: Decision.learnship_equivalent field,
agent persona prompts, opencode.json permissions, test fixtures
- Migrate verification layers from .planning/ to .ci/: structural
checks .ci/ dir + ROADMAP.md, behavioral checks ROADMAP.md
- Fix ollama-local: remove sync require+curl blocking, use async
fetchAvailableModels() in callModel
- Fix opencode.json: use __OPENCODE_DIR__ template tokens, remove
legacy learnship permission entries
- Remove duplicate install script from package.json (keep postinstall)
- Fix quality any-regex false positives (target type annotations only)
- Add backends test coverage: backends.test.ts, tool-registry.test.ts
- Version bump 0.3.0 → 0.4.0
- Artifacts module: rename .planning→.ci internal paths
- Remove dead TODO_PATTERN/FIXME_PATTERN constants
---ci---
phase: 3
milestone: v0.4
status: complete
requirements:
covered: [REQ-09, REQ-10, REQ-11, REQ-13, REQ-14, REQ-17]
partial: []
decisions:
- id: D-001
decision: purge all learnship references from codebase
rationale: project is CI-only, learnship is no longer a dependency
confidence: 0.99
category: scope
alternatives: [keep for historical reference]
- id: D-002
decision: migrate verification from .planning/ to .ci/ paths
rationale: .planning/ is removed schema, all current state lives in .ci/
confidence: 0.95
category: architecture
alternatives: [keep dual-path support]
- id: D-003
decision: use __OPENCODE_DIR__ template tokens in opencode.json
rationale: hardcoded ~ paths fail in containers and non-standard homes
confidence: 0.90
category: implementation_approach
alternatives: [keep tilde expansion]
---/ci---
2.5 KiB
description, color, tools
| description | color | tools | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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. | #FF69B4 |
|
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.
<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 / in multi-project mode
- .ci/ files are in .ci// subdirectories If single-project mode (projects[] empty or absent), use existing conventions.
Before reviewing, load context from git first:
- Run
git log --max-count=10for recent changes - Run
git diff HEAD~3to see the changes being reviewed - Use GitContext.getDecisions() for design decisions that explain choices
- Read
.ci/ARCHITECTURE.mdfor component boundaries - Read
./AGENTS.mdfor 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):
- Check for issues specific to your persona
- Classify each issue by severity: P0 (blocking), P1 (important), P2 (nit)
- Note specific file:line for every finding
- 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>