| name | quality-contracts |
| description | Use when deciding which checks are authoritative for a Hushhtech PR and whether the right proof exists for the changed behavior. |
Hushhtech Quality Contracts Skill
Purpose and Trigger
- Primary scope:
quality-contracts
- Trigger on test selection, proof minimization, and deciding which checks are authoritative for a PR.
- Avoid overlap with
repo-operations and direct implementation skills.
Coverage and Ownership
- Role:
spoke
- Owner family:
oss-contribution-triage
Owned repo surfaces:
tests
vitest.config.ts
docs/reference/quality/pr-impact-checklist.md
Non-owned surfaces:
oss-contribution-triage
repo-operations
frontend
backend
Do Use
- Deciding whether unit, typecheck, build, smoke, or browser proof is authoritative.
- Calling out missing proof in a contributor PR.
- Keeping patch-and-merge bounded to the right validation bundle.
Do Not Use
- Pipeline ownership or workflow debugging.
- Final PR bucket selection without first reasoning about proof.
- Pure product implementation.
Read First
docs/reference/quality/pr-impact-checklist.md
package.json
vitest.config.ts
docs/reference/operations/ci-governance.md
Workflow
- Start from the changed behavior, not from the largest available test suite.
- Select the smallest authoritative proof.
- Escalate to
security-audit if the missing proof involves auth, env, or privileged routes.
Handoff Rules
- Route final bucket selection back to
oss-contribution-triage.
- Route workflow trust questions to
repo-operations.
- Route sensitive security risk to
security-audit.
- Route code fixes to
frontend or backend.
Required Checks
npm test
npx tsc --noEmit
npm run build:web
npm run smoke:ci
npm run test -- tests/communityApiRoute.test.ts tests/communityGcpRuntime.test.ts
For community sensitive-document or NDA-gate changes, the authoritative proof is
split across two lanes: the blocking Sensitive NDA Gate CI/queue job covers API
regressions and verifier syntax, while Deploy to UAT runs the live
npm run verify:sensitive-nda-gate -- --target=uat --expected-min=1 check
against the deployed host.