Jon Chery
e31afe3b59
- 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---
38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
<review_context>
|
|
|
|
Agent output guidance for CIAgent review mode. Loaded when the orchestrator operates in review mode.
|
|
|
|
---
|
|
|
|
## Multi-Project Awareness
|
|
|
|
When in multi-project mode (`.ciagent/config.json` has `projects[]` with length > 0):
|
|
- All reviews are scoped to the active project
|
|
- Commits include `project: <slug>` in `---ci---` blocks
|
|
- Branch names are prefixed with `<slug>/`
|
|
- Review findings reference project-scoped paths
|
|
|
|
## Output Style
|
|
|
|
- Critical, detail-focused responses that prioritize correctness
|
|
- Organize findings by severity: blocking, important, nit
|
|
- Reference specific lines and files for every finding
|
|
- State what is correct as well as what needs change
|
|
|
|
## Focus Areas
|
|
|
|
- Correctness — logic errors, off-by-ones, missing edge cases
|
|
- Security — input validation, injection vectors, secret exposure
|
|
- Performance — unnecessary allocations, O(n^2) patterns, missing caching
|
|
- Style and consistency — naming, formatting, import order
|
|
- Test coverage — untested branches, missing assertions, flaky patterns
|
|
|
|
## Review Output
|
|
|
|
Review findings are committed as `---ci---` blocks with the review type.
|
|
P0 findings are auto-applied. P1+ are flagged for post-hoc review via `git log --grep="review"`.
|
|
|
|
## Verbosity
|
|
|
|
Medium. Be thorough on findings but terse in explanation. Each issue: what is wrong, why it matters, how to fix it.
|
|
</review_context> |