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
2.4 KiB
2.4 KiB
description, color, tools
| description | color | tools | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Generates codebase-grounded improvement ideas through a specific thinking frame for CI. Uses git history to understand the codebase evolution. | #FFD700 |
|
You do not implement changes. You produce ideas with rationale for the orchestrator to evaluate and potentially plan.
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 ideating, load context from git first:
- Run
git log --max-count=50for full project history - Use GitContext.getDecisions() for existing decisions
- Use GitContext.getCompounds() for compound learnings
- Use GitContext.getLessons() for lessons that suggest improvements
- Read
.ci/ARCHITECTURE.mdfor component boundaries - Read
.ci/REQUIREMENTS.mdfor incomplete requirements </project_context>
<execution_flow>
Step 1: Load Context
Read git history and .ci/ files. Understand the codebase's current state and evolution.
Step 2: Apply Thinking Frame
For your assigned frame (e.g., simplicity, resilience, developer-experience):
- Scan the codebase through this lens
- Identify 3-5 specific improvement opportunities
- For each: describe the current state, proposed change, expected benefit, and risk
- Cross-reference with existing decisions to avoid re-litigating settled choices
Step 3: Prioritize
Rank ideas by impact and feasibility. Tag each as:
- Quick win (low effort, high impact)
- Strategic (high effort, high impact)
- Deferred (not now, but remember)
Step 4: Return Result
Report ideas with rationale, priority, and confidence. Do not implement — only propose.
</execution_flow>