- 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---
2.2 KiB
description
| description |
|---|
| Execute an ad-hoc CIAgent task with full agentic guarantees — git context, ---ci--- commits, optional research and verification |
CIAgent Quick
Execute small, ad-hoc tasks with CIAgent guarantees: git context loading, ---ci--- commit blocks, optional research and verification.
Usage: ciagent-quick [description]
Flags:
--research— spawn a focused research agent before execution--verify— verify results after execution--full— research + verify
Step 0: Confirm Active Project
Check ci listProjects() or read .ciagent/config.json to determine if multi-project mode is active.
If .ciagent/config.json has projects[] with length > 0:
- Confirm
active_projectis correct - If not, set it with
ci setActiveProject(<slug>) - All commit messages must include
project: <slug>in---ci---block
If single-project mode: proceed with existing conventions.
Step 1: Get Task Description
If provided as argument, use it. Otherwise ask: "What do you want to do?"
Step 2: Load Git Context
git log --max-count=20
git branch -a
Use GitContext.reconstructState() to understand project state.
Check that .ciagent/config.json exists. If missing: stop, run ciagent-init first.
Step 3: Research (only with --research or --full)
Delegate to ci-researcher for a focused research pass:
- What libraries or approaches are relevant?
- What pitfalls to avoid?
- Existing patterns in the codebase?
Step 4: Execute
Implement the task directly. Key principles:
- Minimal diff — change only what is necessary
- Commit with
---ci---block:
feat(P##): [task description]
---ci---
phase: [N]
milestone: [vX.X]
status: execute
---/ci---
Use the current phase and milestone from GitContext.reconstructState().
Step 5: Verify (only with --verify or --full)
Delegate to ci-verifier:
- Does the change work?
- Does typecheck/lint pass?
- Do existing tests still pass?
Step 6: Commit Summary
Final commit if multiple changes were made:
docs(P##): quick task — [description]
---ci---
phase: [N]
milestone: [vX.X]
status: execute
lessons:
- [lesson if any]
---/ci---
Report completion with next suggested action.