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---
2.7 KiB
description
| description |
|---|
| Verify CIAgent project deliverables against requirements — structural, behavioral, security, and quality checks |
CIAgent Verify
Run the CIAgent verification pipeline against the current or specified phase. Four layers: structural, behavioral, security, quality.
Usage: ciagent-verify [phase_number]
If no phase specified, verifies the current phase.
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 for this verification - If not, set it with
ci setActiveProject(<slug>) - Scope verification to the active project
- All commit messages must include
project: <slug>in---ci---block
If single-project mode: proceed with existing conventions.
Phase Boundary Checkpoint: Between phases, all state is committed to git, context is reset, and the next phase begins with fresh git log context. Verify that the current verification aligns with the reconstructed state.
Step 1: Load Git Context
git log --max-count=30
git branch -a
Determine the phase to verify from git context or argument.
Step 2: Structural Verification (Layer 1)
Check:
- All files referenced in plans exist on disk
- All imports resolve (no dangling references)
- No stub implementations or TODO placeholders
- All declared exports actually exist
Run: npm run typecheck or equivalent
Run: npm run build or equivalent
Step 3: Behavioral Verification (Layer 2)
Check:
- All tests pass:
npm test - Must-have criteria from plan frontmatter are met
- Requirement coverage: each REQ-ID for this phase is covered
For unverifiable items: auto-generate test scripts.
Step 4: Security Verification (Layer 3)
STRIDE analysis:
- Spoofing, Tampering, Repudiation, Info Disclosure, Denial of Service, Elevation of Privilege
Auto-disposition: low=accept, medium=mitigate, high=escalate.
Step 5: Quality Verification (Layer 4)
Multi-persona code review:
- Correctness: logic errors, edge cases
- Testing: coverage gaps, flaky tests
- Security: input validation, injection vectors
- Performance: unnecessary allocations, O(n^2)
- Maintainability: naming, structure, coupling
- Adversarial: attack surface, abuse cases
P0 fixes are auto-applied. P1+ are flagged for post-hoc review.
Step 6: Commit Results
verify(P##): [passed|gaps_found]
---ci---
phase: [N]
milestone: [vX.X]
status: verify
requirements:
covered: [REQ-01, REQ-02]
partial: [REQ-03]
lessons:
- [lesson from verification]
---/ci---
Step 7: Return Result
Report verification score, any gaps found, and next steps.