docs(rebrand): rename & rebrand CI → CIAgent across all documentation, templates, and scripts
- README.md: title, project name, CLI commands, .ci/ → .ciagent/, ci-files → ciagent-files, CI Modification → CIAgent Modification - AGENTS.md: title, project name, architecture tree, agent count (18→19), test count (25→31 suites, 218→370 tests), version (0.4.0→0.6.0), ci-files → ciagent-files, CIConfig → CIAgentConfig, CiMetadata → CIAgentMetadata, .ci/ → .ciagent/ - templates/DECISIONS.md: .ci/audit/ → .ciagent/audit/, ci audit → ciagent audit - scripts/postinstall.js: CI postinstall → CIAgent postinstall - scripts/install.sh: CI → CIAgent, ci-init → ciagent-init, INSTALL COMPLETE banner - opencode/ci/workflows/*.md (11 files): .ci/ → .ciagent/, CI → CIAgent project name, ci-command → ciagent-command usage lines - opencode/ci/references/*.md (5 files): .ci/ → .ciagent/, CI → CIAgent project name, ci-files → ciagent-files references - opencode/ci/contexts/*.md (3 files): .ci/ → .ciagent/, CI → CIAgent project name - opencode/agents/ci-*.md (18 files): .ci/ → .ciagent/, CI → CIAgent project name - opencode/command/ci-*.md (11 files): CI → CIAgent project name Preserved: ---ci---/---/ci--- markers, opencode/ci/ dir paths, ci-*.md filenames, ci listProjects()/ci setActiveProject() API names, repo URLs ---ci--- phase: 1 milestone: v0.6 plan: 01-01 task: 01-01-01 status: execute ---/ci---
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
---
|
||||
description: Orchestrates the full CI pipeline by iterating through pipeline stages, loading context from the git log first, and delegating to specialized agents. The orchestrator is CI-specific — it drives the SPECIFY → CLARIFY → RESEARCH → PLAN → EXECUTE → VERIFY → COMPLETE flow.
|
||||
description: Orchestrates the full CIAgent pipeline by iterating through pipeline stages, loading context from the git log first, and delegating to specialized agents. The orchestrator is CIAgent-specific — it drives the SPECIFY → CLARIFY → RESEARCH → PLAN → EXECUTE → VERIFY → COMPLETE flow.
|
||||
color: "#00BFFF"
|
||||
tools:
|
||||
read: true
|
||||
@@ -11,9 +11,9 @@ tools:
|
||||
---
|
||||
|
||||
<role>
|
||||
You are the CI orchestrator. You drive the full CI pipeline by iterating through pipeline stages, making git-first context loading decisions, and delegating to specialized agents.
|
||||
You are the CIAgent orchestrator. You drive the full CIAgent pipeline by iterating through pipeline stages, making git-first context loading decisions, and delegating to specialized agents.
|
||||
|
||||
CI operates autonomously after the clarify phase. You never pause for human checkpoints unless a decision falls below the confidence threshold or an escalation hook is triggered.
|
||||
CIAgent operates autonomously after the clarify phase. You never pause for human checkpoints unless a decision falls below the confidence threshold or an escalation hook is triggered.
|
||||
|
||||
Your job: Execute stages in order, collect PhaseResult for each, handle errors via ErrorRecovery, and produce a final project outcome.
|
||||
|
||||
@@ -22,11 +22,11 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</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
|
||||
If .ciagent/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ciagent/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
|
||||
- .ciagent/ files are in .ciagent/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before any operation, load project context from git first:
|
||||
@@ -37,9 +37,9 @@ Before any operation, load project context from git first:
|
||||
4. Use GitContext.getEscalations() for any pending escalations
|
||||
5. Use GitContext.getRequirementsCoverage() for covered/partial requirements
|
||||
6. Use GitContext.getLessons() for learned lessons
|
||||
7. Read `.ci/config.json` for autonomy level and parallelization settings
|
||||
8. Read `.ci/PROJECT.md` for project vision and constraints
|
||||
9. Read `.ci/ROADMAP.md` for phase breakdown and success criteria
|
||||
7. Read `.ciagent/config.json` for autonomy level and parallelization settings
|
||||
8. Read `.ciagent/PROJECT.md` for project vision and constraints
|
||||
9. Read `.ciagent/ROADMAP.md` for phase breakdown and success criteria
|
||||
</project_context>
|
||||
|
||||
<execution_flow>
|
||||
|
||||
Reference in New Issue
Block a user