skills.rest
xxih
xxihCOMMUNITY
Explore all skills by this author →
GitHub

quality-verify

Run verification commands and record results in .quality/quality-check.md.

1|Updated Mar 18, 2026
Search Tags:#testing#verification#quality#evidence#code#readiness#ci
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill quality-verify-xxih
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-verify
Source: https://github.com/xxih/ai-harness-zh/tree/main/packages/quality-workflows/targets/codex/skills/quality-verify
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill quality-verify-xxih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents premature completion claims by requiring fresh, verifiable evidence before a task is marked ready or completed.

Core Features & Use Cases

  • Evidence Generation: Runs full verification commands (build, tests, diff, lint, etc.) and captures exit codes, summaries, and failure details.
  • Decision Gate: Returns a clear ready or not‑ready status based on the freshness and completeness of the evidence.
  • Record Keeping: Writes verification results to .quality/quality-check.md or updates existing task records.
  • Use Case Example: Before merging a pull request, a developer invokes this skill to ensure that the latest build passes, all tests succeed, and no new lint issues are introduced, guaranteeing that the codebase is truly ready.

Quick Start

Ask the assistant to run the quality‑verify skill before marking the task as ready.

Frequently Asked Questions about quality-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code readiness with fresh evidence before a commit?▼

To verify code readiness, execute full verification commands like build and test suites, capture exit codes and summaries, and record results in .quality/quality-check.md to prevent premature completion claims.

What is quality verification evidence and why is it needed for pull requests?▼

Quality verification evidence is fresh output from commands like tests and lint checks that confirms a codebase is truly ready, preventing premature completion claims before pull request merges or task transitions.

How do I generate verification records for CI pipelines?▼

Generate verification records by running full build, test, diff, and lint commands, then capture their exit codes and failure details to write a decision gate summary into .quality/quality-check.md.

Does this readiness verification approach work without external CI dependencies?▼

Yes, readiness verification works without external dependencies by executing local verification commands directly, capturing exit codes and summaries, and returning a clear ready or not-ready status gate.

What's the best way to prevent premature task completion claims in software engineering?▼

The best way to prevent premature claims is requiring fresh, verifiable evidence by running full verification commands, capturing exit codes, and returning a clear ready or not-ready decision status.

Related Skills

Explore More Software Engineering Skills→
gugug168gugug168

verification-loop

Run end-to-end code verification covering builds, types, lint, tests, security, and diffs.

Community
Intermediate
xxihxxih
1

quality-review

Review code changes and classify issues into Critical, Important, or Minor categories.

Community
Intermediate
imbue-aiimbue-ai
1

handle-mng-agent_states

Process managed agent lifecycle state events and trigger automated responses.

Official
Intermediate
gear-foundationgear-foundation
17

gtest-tdd-loop

Validate Gear/Vara behavior changes with local gtest red-green loops.

Official
Intermediate