Run any Skill in Manus with one click

quality-verify

Stars6

Forks0

UpdatedMay 22, 2026 at 07:27

Validate strict DAE quality gates after implementation-affecting changes, require machine-readable evidence, and write the quality-gate summary before completion or release.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kdoronin

kdoronin/dae_codex

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	quality-verify
description	Validate strict DAE quality gates after implementation-affecting changes, require machine-readable evidence, and write the quality-gate summary before completion or release.

DAE Quality Verify

Use this skill when implementation/scaffold/config/test work has happened, when quality_dirty=true, or before any completion/release/commit/push claim.

Contract

Quality verification is evidence-driven. Do not satisfy required gates with prose-only claims.

Strict defaults require:

ATDD acceptance stream evidence;
independent unit stream evidence;
CRAP analyzer evidence;
architecture check evidence;
refine review evidence;
branch hygiene evidence;
progress breadcrumb evidence;
durable handoff evidence;
duplicate-detection evidence;
test-impact evidence;
generated acceptance immutability evidence;
mutation evidence when configured, hardening is active, or CRAP/risk triggers it.

Workflow

Inspect current status:

python3 plugins/engineer/scripts/dae_guard.py quality-status
python3 plugins/engineer/scripts/dae_guard.py quality-required-evidence

Produce missing evidence with the owning workflows:
- atdd: acceptance stream, unit stream, generated acceptance immutability, mutation/hardening.
- engineer: arch-check, refine, branch hygiene, progress, handoff, duplicate detection, test impact.
- crap-analyzer: CRAP scoring for changed code.
Write evidence under:
```
features/<feature>/evidence/quality/<gate>.json
```
Every required evidence file must include schema_version, gate, status, generated_at, feature, and changed_files.

Validate and summarize:

python3 plugins/engineer/scripts/dae_guard.py quality-verify

Continue only if quality-verify exits 0 and writes a passing quality-gate-summary.json.

CRAP Evidence

CRAP is required by default after implementation-affecting edits. Missing coverage must not silently pass strict mode. The CRAP evidence file must include thresholds and summary fields, including summary.max_crap_score and summary.high_risk_findings.

If CRAP returns warning-level risk or high-risk findings, mutation evidence becomes required before completion.

More from this repository

same repository

crap-analyzer

kdoronin/dae_codex

Analyze changed code for complex, under-tested functions using CRAP scoring; produce ranked refactor and test recommendations.

2026-05-226

atdd-mutate

kdoronin/dae_codex

This skill should be used when the user asks to "run mutation testing", "mutate my code", "kill mutants", "check test quality", "find surviving mutants", "verify test effectiveness with mutations", "run stryker", "run mutmut", "run pitest", "set up mutation testing", "how good are my tests", "are my tests catching bugs", or mentions mutation testing, mutation score, or mutant survival in the context of testing. It adds a third validation layer to the ATDD workflow: after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies that tests actually catch bugs.

2026-05-226

atdd

kdoronin/dae_codex

This skill should be used when the user asks to "build a feature", "implement a feature", "add functionality", "start development", "write acceptance tests", "write specs", "use ATDD", "use TDD with acceptance tests", or begins any feature implementation work. Also available as the atdd plugin's main skill. Enforces the Acceptance Test Driven Development workflow: write Given/When/Then specs before code, generate a project-specific test pipeline, and maintain two test streams.

2026-05-226

atdd-team

kdoronin/dae_codex

This skill should be used when the user asks to "build a feature with a team", "use ATDD with agents", "create an ATDD team", "set up a team for ATDD", "orchestrate agents for ATDD", "use team-based development", "coordinate agents for feature development", "run the ATDD workflow with teammates", "add ATDD to my team", "extend my team with ATDD", "join the team with ATDD agents", "add spec-writer and reviewer to the team", or "add ATDD roles to the existing team". It orchestrates a six-phase ATDD workflow — spec writing, spec review, pipeline generation, implementation, refine, verify & harden — spawning a fresh agent per phase so no agent erodes across a long-running feature.

2026-05-226

kill-mutants

kdoronin/dae_codex

Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.

2026-05-226

mutate

kdoronin/dae_codex

Use as a thin compatibility skill when the user asks for the old mutate command; delegate to atdd-mutate for mutation testing and differential mutation workflow.

2026-05-226

DAE Quality Verify

Use this skill when implementation/scaffold/config/test work has happened, when quality_dirty=true, or before any completion/release/commit/push claim.

Contract

Quality verification is evidence-driven. Do not satisfy required gates with prose-only claims.

Strict defaults require:

ATDD acceptance stream evidence;

independent unit stream evidence;

CRAP analyzer evidence;

architecture check evidence;

refine review evidence;

branch hygiene evidence;

progress breadcrumb evidence;

durable handoff evidence;

duplicate-detection evidence;

test-impact evidence;

generated acceptance immutability evidence;

mutation evidence when configured, hardening is active, or CRAP/risk triggers it.

Workflow

Inspect current status:

python3 plugins/engineer/scripts/dae_guard.py quality-status
python3 plugins/engineer/scripts/dae_guard.py quality-required-evidence

Produce missing evidence with the owning workflows:

atdd: acceptance stream, unit stream, generated acceptance immutability, mutation/hardening.
engineer: arch-check, refine, branch hygiene, progress, handoff, duplicate detection, test impact.
crap-analyzer: CRAP scoring for changed code.

Write evidence under:

features/<feature>/evidence/quality/<gate>.json

Every required evidence file must include schema_version, gate, status, generated_at, feature, and changed_files.

Validate and summarize:

python3 plugins/engineer/scripts/dae_guard.py quality-verify

Continue only if quality-verify exits 0 and writes a passing quality-gate-summary.json.

CRAP Evidence

If CRAP returns warning-level risk or high-risk findings, mutation evidence becomes required before completion.