Cross-Stack Quality Gates
Discover the project's contract before running validation. Read gate discovery only for the stacks present in the target scope.
Workflow
- Inspect repository instructions, manifests, CI configuration, and documented scripts.
- Determine which components changed and which gate owns each relevant invariant.
- If an installed stack profile matches the component, use it for stack-specific hazards, compatibility, and gate judgment. The profile does not override repository instructions.
- Choose the narrowest useful sequence, normally fast static checks before slower tests and builds.
- Run commands exactly as the repository defines them. Do not silently substitute package managers, add flags, rewrite snapshots, format files, apply Terraform, or update dependencies.
- Record command, working directory, exit status, duration when material, and the first actionable failure.
- Distinguish a missing gate from a passing gate. Do not skip an unavailable command and report the suite green.
- Report environment restrictions separately from product failures.
Done when
The run is done when every required gate for the changed components has a recorded result or is reported as unavailable, and the verdict is PASS, FAIL, or INCOMPLETE as the output rule defines. An unavailable gate makes the verdict INCOMPLETE; it is not a reason to stop. Stop and ask only when a gate needs a mutating step or credentials the task did not authorize, or the repository is not one the user has said they trust.
Scope rules
- Repository scripts, hooks, and tests run code with your permissions. In a repository the user has not said they trust, such as a fresh clone or someone else's branch, read what a command runs and ask before running it.
- A monorepo may require multiple component-specific gates; do not run every workspace blindly.
- Builds may create ignored artifacts or caches but must not rewrite tracked source.
- SQL validation must state whether it was syntax/static only or executed against a real engine.
- Terraform validation is not an apply. Plans are proposals and must not be reported as deployed state.
- Simulator or preview checks do not prove device, production, or provider behavior.
Output
Lead with PASS, FAIL, or INCOMPLETE as derived from the required gates. Keep the
complete gate table with component, command, result, and evidence. Include
unavailable checks, coverage gaps, and the first actionable failure. A missing
required gate cannot become a pass through summarization.
Read the original acceptance example when checking this behavior.
Example
Synthetic example; not an observed client result.
Input: At synthetic revision B, the supplied unit-test receipt records 12 passes. The repository requires an integration check, but its service is unavailable.
Output: INCOMPLETE at B.
| Component |
Command |
Result |
Evidence |
| Unit |
python3 -m unittest discover -s tests/unit |
PASS |
Supplied receipt at B: 12 passes |
| Integration |
python3 -m unittest discover -s tests/integration |
NOT RUN |
Required service unavailable |
The integration gate is the first actionable blocker. Its behavior remains unverified; repeat that gate when the service is available. No completion claim is supported yet.
1---2name: run-project-checks3description: "Finds and runs repository checks when asked to run tests, check the build, or verify changes; follows actual CI and scripts rather than assuming one universal test command. Loads before file inspection when the request matches."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/run-project-checks7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "implicit"11 provenance: "adapted"12 risk_class: "bounded-execution"13---1415# Cross-Stack Quality Gates1617Discover the project's contract before running validation. Read [gate discovery](references/gate-discovery.md) only for the stacks present in the target scope.1819## Workflow20211. Inspect repository instructions, manifests, CI configuration, and documented scripts.222. Determine which components changed and which gate owns each relevant invariant.233. If an installed stack profile matches the component, use it for stack-specific hazards, compatibility, and gate judgment. The profile does not override repository instructions.244. Choose the narrowest useful sequence, normally fast static checks before slower tests and builds.255. Run commands exactly as the repository defines them. Do not silently substitute package managers, add flags, rewrite snapshots, format files, apply Terraform, or update dependencies.266. Record command, working directory, exit status, duration when material, and the first actionable failure.277. Distinguish a missing gate from a passing gate. Do not skip an unavailable command and report the suite green.288. Report environment restrictions separately from product failures.2930## Done when3132The run is done when every required gate for the changed components has a recorded result or is reported as unavailable, and the verdict is PASS, FAIL, or INCOMPLETE as the output rule defines. An unavailable gate makes the verdict INCOMPLETE; it is not a reason to stop. Stop and ask only when a gate needs a mutating step or credentials the task did not authorize, or the repository is not one the user has said they trust.3334## Scope rules3536- Repository scripts, hooks, and tests run code with your permissions. In a repository the user has not said they trust, such as a fresh clone or someone else's branch, read what a command runs and ask before running it.37- A monorepo may require multiple component-specific gates; do not run every workspace blindly.38- Builds may create ignored artifacts or caches but must not rewrite tracked source.39- SQL validation must state whether it was syntax/static only or executed against a real engine.40- Terraform validation is not an apply. Plans are proposals and must not be reported as deployed state.41- Simulator or preview checks do not prove device, production, or provider behavior.4243## Output4445Lead with PASS, FAIL, or INCOMPLETE as derived from the required gates. Keep the46complete gate table with component, command, result, and evidence. Include47unavailable checks, coverage gaps, and the first actionable failure. A missing48required gate cannot become a pass through summarization.4950Read [the original acceptance example](references/continuity-example.md) when checking this behavior.5152## Example5354Synthetic example; not an observed client result.5556Input: At synthetic revision B, the supplied unit-test receipt records 12 passes. The repository requires an integration check, but its service is unavailable.5758Output: INCOMPLETE at B.5960| Component | Command | Result | Evidence |61| --- | --- | --- | --- |62| Unit | `python3 -m unittest discover -s tests/unit` | PASS | Supplied receipt at B: 12 passes |63| Integration | `python3 -m unittest discover -s tests/integration` | NOT RUN | Required service unavailable |6465The integration gate is the first actionable blocker. Its behavior remains unverified; repeat that gate when the service is available. No completion claim is supported yet.