skills.rest
juanca202
juanca202COMMUNITY
Explore all skills by this author →
Website𝕏@juanca202GitHub

quality-check

Runs automated stack checks and emits a verdict report with next actions.

Updated May 8, 2026
Search Tags:#testing#static analysis#linting#code coverage#quality gate#build verification#ci validation
One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill quality-check-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-check
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/quality-check
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill quality-check-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Before merging or opening a pull request, teams need to know whether the repository passes its automated quality gates — type checking, linting, unit tests, coverage, build, e2e, and static analysis — without manually running and interpreting each tool. This Skill executes the full battery of checks adapted to the detected stack and produces a single verdict (APPROVED, REJECTED, or INCOMPLETE) with a written report. ## Core Features & Use Cases - Stack-adaptive check execution: Detects the ecosystem (Node, Java/Kotlin, Python, Go, Rust, .NET, PHP) from the project manifest and runs the applicable checks with the correct commands and output parsing. - Verdict and audit report: Classifies each check as blocking, conditional, or informative, computes a canonical verdict, and writes a report to docs/audits/quality-check.md plus a reusable test-run cache (quality-check-run.json) consumed by other verification skills. - Controlled fixing: By default it only audits and asks before correcting failures, delegating fixes to the implementation workflow; it never commits, pushes, or merges on its own. - Use Case: Before creating a PR, ask the agent to run the quality checks on your branch; it executes the test suites, linters, and build, then delivers a report stating exactly what failed and what is needed to reach an approved state. ## Quick Start Ask the agent to run the quality checks on this repository and report whether it is ready for a pull request.

Frequently Asked Questions about quality-check

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

FAQPage Schema
How do I run all automated tests and checks before a pull request?▼

Invoke the quality check on your branch and it runs type checking, linting, unit tests, coverage, build, e2e, and static analysis in sequence. It then emits a verdict of APPROVED, REJECTED, or INCOMPLETE with a written report in docs/audits/quality-check.md.

What checks does a pre-merge quality gate typically include?▼

A typical gate covers type checking, linter errors, unit tests, code coverage, build, e2e tests, and static analysis such as Sonar. Only unit tests and coverage are fixed; the rest apply based on the detected stack and the repository testing standard.

Does it support monorepos with multiple modules?▼

Yes, it detects multiple manifests and selects one module based on the user-indicated directory or the diff paths, asking when ambiguous. It audits only the chosen module unless you explicitly request all modules.

Can it run checks on a repository without spec-driven artifacts?▼

Yes, it requires only a recognizable repository root with a detectable stack manifest. No plugin artifacts like specs, user stories, or branch conventions are needed, and the run and verdict are identical without them.

Why does the verdict come back INCOMPLETE instead of APPROVED?▼

INCOMPLETE means no check failed but at least one required check was skipped because its tool or configuration was missing or broken. Resolve the tooling for the skipped check and rerun to reach APPROVED.

Will it fix failing tests automatically?▼

By default it only reports failures and asks before correcting anything. Setting verification.qualityCheck.confirmFix to never in .sdd-devkit/settings.json allows it to apply fixes directly and rerun the full battery.

Related Skills

Explore More Software Engineering Skills→
evolution-foundationevolution-foundation
520

dev-release

Generate a changelog, bump semantic versions, and create a release commit and tag.

Official
Advanced
ablyably
5

code-review-all

Coordinate parallel subagent reviews and synthesize severity-grouped findings into one verdict.

Official
Advanced
hujianbesthujianbest
51

hf-verify

Execute three-layer verification with smoke tests, code review, and mechanical gates.

Community
Advanced
4lerman4lerman

ci-cd-pipeline-builder

Detect repository stacks and generate CI/CD pipeline templates for GitHub Actions and GitLab CI.

Community
Advanced