verify-task
Verify completed Astra work with evidence. Uses canonical Work criteria and checks when present; otherwise derives targeted gates from the diff and changed behavior.
Datos de origen
- Repositorio
- matrixorigin/Astra
- Última actividad en el origen
- 3 de septiembre de 2026 a las 04:27
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 30
- Forks
- 5
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- verify-task
- description
- Verify completed Astra work with evidence. Uses canonical Work criteria and checks when present; otherwise derives targeted gates from the diff and changed behavior.
- user_invocable
- true
- when_to_use
- When the user wants to verify that a completed task actually works, run focused tests/lint/build checks, or produce a delivery report.
- arguments
- [{"name":"TASK","description":"last, task ID, or natural language description of what should work.","required":false},{"name":"SCOPE","description":"quick, full, or custom. Default: full.","required":false}]
- allowed_tools
- ["bash","read_file","grep","glob"]
# Verify Task
Verification is evidence, not optimism. Use the strongest existing contract; if no
contract exists, derive checks from the diff and changed behavior.
## Task
$ARGUMENTS
## Phase 1: Determine Verification Source
1. Check current work:
```bash
git status --short
git diff --stat
git diff --name-only
```
2. If the change is backed by durable Work, use the canonical service types:
| Concept | Source |
| --- | --- |
| Generic command verifier schema | `crates/services/src/verification.rs` |
| Durable Work domain and lifecycle | `crates/services/src/work.rs` |
| Work checks and acceptance | `crates/services/src/work/acceptance.rs`, `crates/services/src/work/repository.rs` |
| CLI Work projection | `crates/astra-cli/src/cli/work_command.rs` |
| Verification journal event | `crates/services/src/session_journal.rs` |
Current verifier kinds are `command`, `command_output`, `file_exists`, `grep_check`,
`build_pass`, `test_pass`, `read_file_contains`, `llm_judge`, and `composite`.
3. If there is no contract, create acceptance criteria from changed behavior:
- What user/system behavior changed?
- What state or output proves it?
- What failure path matters?
- Which crate/module owns it?
## Phase 2: Select Gates
Run only gates that can be affected by the change.
| Change | Required gate |
| --- | --- |
| Skill/docs only | Frontmatter parse, metadata JSON parse, stale path scan, `.claude`/`.agent` sync; no Rust build |
| Rust formatting only | `cargo fmt --check` |
| Single Rust crate | `cargo check -p <crate>` plus focused tests |
| Shared Rust API | `cargo check --workspace --all-targets` plus affected tests |
| Runtime/server lifecycle | Focused runtime tests, then `cargo check -p astra-runtime` |
| Turn/tool/prompt behavior | Focused turn/runtime tests plus prompt/tool surface assertions |
| Services/storage/MatrixOne | Focused services tests; online DB check only when configured and relevant |
| CLI/TUI | Focused `astra-cli` tests or command dry run |
| Frontend/SDK | Relevant package script or existing make target |
| Shell/deployment | Exact owning make/script dry run |
Run raw cargo commands from the repository root; `Cargo.toml` is the workspace manifest.
## Phase 3: Execute And Interpret
For each criterion record:
- command or inspection performed;
- pass/fail/inconclusive;
- evidence line or output summary;
- skipped reason if not run.
If a command fails, stop broadening and diagnose the failed gate first. A later broad
test cannot make an earlier required failure irrelevant.
## Phase 4: Delivery Report
Use this shape:
```text
Verdict: verified | failed | inconclusive | verified with warnings
Criteria:
- PASS <criterion> - <evidence>
- FAIL <criterion> - <evidence and likely owner>
- SKIP <criterion> - <reason>
Commands:
- <command> -> <result>
Residual Risk:
- <only real gaps, such as online DB not available>
```
Verdict rules:
| Evidence | Verdict |
| --- | --- |
| All required criteria pass | verified |
| Required pass, optional/skipped checks have justified residual risk | verified with warnings |
| Any required criterion fails | failed |
| Verification could not run enough evidence to judge | inconclusive |
Ver en GitHub