بنقرة واحدة
dod-verify
Run DoD evidence checks against a ticket contract and generate a verification receipt
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Run DoD evidence checks against a ticket contract and generate a verification receipt
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Dispatch a background worker with role-templated prompt and auto-populated collision fences
Comprehensive system health monitoring — checks agent performance, database, Kafka topics, pattern discovery, and service status across the ONEX platform
Orchestrate a Claude Code agent team to autonomously work a Linear epic across multiple repos
Autonomous per-ticket pipeline that chains ticket-work, local-review, PR creation, CI watching, PR review loop, integration verification gate, and auto-merge into a single unattended workflow with Slack notifications and policy guardrails
Full autonomous audit-debug-fix loop for all dashboard pages — Playwright recon, parallel systematic-debug, fix, PR, Linear ticket, re-audit, iterate until clean. Supports local and cloud targets with optional post-fix redeployment.
Full post-release runtime redeploy — syncs bare clones, updates Dockerfile plugin pins, rebuilds Docker runtime, seeds Infisical, and verifies health
| name | dod-verify |
| description | Run DoD evidence checks against a ticket contract and generate a verification receipt |
| level | intermediate |
| debug | false |
| category | verification |
| tags | ["dod","evidence","verification","contracts","quality"] |
| author | OmniClaude Team |
| args | [{"name":"ticket_id","description":"Linear ticket ID (e.g., OMN-1234)","required":true},{"name":"--contract-path","description":"Override path to contract YAML (default auto-detect)","required":false}] |
Skill ID: onex:dod-verify
Version: 1.0.0
Owner: omniclaude
Ticket: OMN-5174
Run DoD evidence checks for a ticket and generate a structured verification receipt. This is the voluntary verification entry point that agents can invoke before marking a ticket as Done.
/dod-verify OMN-1234
/dod-verify OMN-1234 --contract-path contracts/OMN-1234.yaml
Locate ticket contract:
--contract-path is provided, use that path directly$ONEX_CC_REPO_PATH/contracts/{ticket_id}.yaml/generate-ticket-contract {ticket_id} firstLoad contract and extract dod_evidence[]:
dod_evidence is empty or missing, report "No DoD evidence items to verify"
and exit cleanlyRun evidence checks:
Use the shared runner at plugins/onex/skills/_lib/dod-evidence-runner/dod_evidence_runner.py:
from dod_evidence_runner import run_dod_evidence, write_evidence_receipt
result = run_dod_evidence(contract["dod_evidence"])
receipt_path = write_evidence_receipt(ticket_id, contract_path, result)
Write evidence receipt:
Receipt is written to .evidence/{ticket_id}/dod_report.json in the current
working directory. This receipt is checked by the PreToolUse completion guard hook.
Output human-readable summary:
DoD Evidence Report for OMN-1234
=================================
| # | Description | Status | Duration |
|---|------------|--------|----------|
| dod-001 | Tests exist and pass | verified | 1.2s |
| dod-002 | Config file created | failed | 0.1s |
| dod-003 | API health check | skipped | - |
Summary: 1 verified, 1 failed, 1 skipped (3 total)
Receipt: .evidence/OMN-1234/dod_report.json
Next steps:
- Fix dod-002: No files matching pattern config/*.yaml
- dod-003 was skipped (endpoint checks require live infra)
dod_verify phase calls this same runnerdod_evidence[] from Linear DoDdod_evidence: report cleanly, exit 0failed with timeout message