# Validate Deliverable Quality Before Release

Final checks often miss consistency, security, or completeness gaps. This skill guides Claude, Codex, and Claude Code through a scored review before delivery.

## Install

```bash
npx skillstore add abejitsu/quality-verify
```

## Metadata

- Status: approved
- Slug: abejitsu-quality-verify
- Skillstore revision: r1
- Version status: missing
- Tree hash: 4397d637a1992ff45327eeea3ef5f98c1715ad9ccf44485f710df695d110b5ba
- Author: AbeJitsu
- GitHub username: AbeJitsu
- License: MIT
- Repository: https://github.com/AbeJitsu/Game-Settings-Panel/tree/main/.claude/skills/quality-verify
- Ref: d46e62089a6dfc9e14ea02eebd9b8e2ad2dfe1f4
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/abejitsu-quality-verify
- Manifest: https://skillstore.pages.dev/api/skills/abejitsu-quality-verify/manifest

## Capabilities

- Evaluates deliverables across completeness, correctness, consistency, performance, security, and maintainability.
- Applies a scoring rubric with thresholds for ready, minor fixes, and major revision.
- Adapts checks to project standards through the referenced StandardsRepository pattern.
- Lists specific issues with critical, major, and minor severity groupings.
- Gives delivery recommendations based on the final quality score.

## Use Cases

- Final Code Review: Check a feature before handoff for completeness, runtime risk, security basics, and maintainability.
- Documentation Handoff Check: Score API or product documentation for completeness, consistency, clarity, and missing examples.
- Release Readiness Gate: Apply one rubric before delivery so reviewers see issues, severity, score, and recommendation.

## Prompt Templates

### Basic Final Check

```
Use quality-verify to review this deliverable. Score each applicable dimension and tell me whether it is ready to deliver.
```

### Standards-Based Review

```
Use quality-verify with our project standards. Identify missing requirements, score each dimension, and list required fixes before delivery.
```

### Cross-Artifact Audit

```
Use quality-verify on the feature and its documentation. Compare behavior, examples, edge cases, and security expectations before recommending delivery.
```

### Strict Release Gate

```
Use quality-verify as a release gate. Apply strict scoring, separate critical, major, and minor issues, and recommend ship or revise.
```

## Limitations

- It depends on the model's ability to inspect the submitted deliverable.
- It does not run tests or scanners by itself.
- It cannot verify external facts without current sources.
- It needs clear user standards for strict project-specific checks.

## Best Practices

- Provide the full deliverable and any project standards before running the skill.
- Ask for separate evidence for each critical or major issue.
- Use the score as a decision aid, not as the only review authority.

## Anti Patterns

- Do not use the skill as a replacement for automated tests.
- Do not accept vague issues without specific locations or examples.
- Do not force every dimension when it does not apply to the deliverable.

## Security Audit

- Audited at: 2026-07-07T17:29:50.264\+00:00
- Summary: Static findings are false positives from Markdown code fences and an inline path reference in SKILL.md. The skill provides a quality verification rubric and does not instruct command execution, network access, secret access, or reconnaissance. No semantic security findings were found.

## Stats

- Views: 182
- Downloads: 8
- Favorites: 0
- Popularity score: 0