---
name: qierkang/project-verification
source: https://app.decimal.ai/s/qierkang-project-verification@1/SKILL.md
source_sha256: 8f185388b95c
---

# Project Verification

Verification must match the changed surface and produce real evidence.

## Read Order

1. Read root and affected package `package.json` files; never assume scripts exist.
2. Read [`references/verification-matrix.md`](references/verification-matrix.md).
3. Inspect current changes to choose the narrowest checks that cover them.

## Workflow

1. Run focused tests when the repository exposes an applicable test command.
2. Run the affected package build.
3. Expand to the root build for shared or cross-package changes.
4. Validate both default and `standalone-infra` Docker Compose configurations when deployment files change.
5. Use HTTP, browser, or screenshot evidence when the request changes runtime or visual behavior.
6. Report commands, results, and anything skipped or blocked.

## Guardrails

- A passing typecheck is not runtime proof.
- A healthy login or process is not proof that the requested workflow works.
- Do not hide failed checks behind unrelated passing checks.
- Do not claim coverage percentages unless a real coverage tool produced them.