comet guard is a stable phase check command. It will check the files, fields and validation evidence required for the current phase.
Basic form
--apply is not brought. When using --apply, after the check is passed, the status script will be entrusted to advance the phase.
Common examinations
- open: Whether the proposal, design, tasks and delta spec are complete.
- design: Does the Design Doc exist?
- build: Check whether
build_mode,isolation,tdd_mode,review_mode, etc. meet the constraints and run the automatically detected project build checks. - verify: Verify whether the report and verification results are available.
- archive: Has the verification been passed and the final confirmation been completed?
Construction check
During the build phase, thebuild_command or verify_command configuration fields will no longer be read. guard will automatically detect build methods based on project files, such as npm run build in package.json, Maven or Cargo.
If build_command/verify_command are still retained in the .comet.yaml of change, guard will reject them as unknown fields. When a fixed team-level verification command is required, it is recommended to place it in the project’s own script system. When the entry cannot be automatically inferred, first run the command in reality, and then use comet state record-check to record the evidence. guard will verify this record.
The installation package still includes
comet-guard.mjs compatible launcher, but for general use and Agent commands, Comet-Guard should be preferred.