quality

Run all quality gates and report detailed status for software projects.

Updated May 24, 2025
One-click install
npx skills add https://github.com/lemeb/python-library-cookiecutter --skill quality-lemeb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/lemeb/python-library-cookiecutter/tree/main/%7B%7Bcookiecutter.project_slug%7D%7D/.claude/skills/quality
Command: npx skills add https://github.com/lemeb/python-library-cookiecutter --skill quality-lemeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end quality verification to ensure code quality across linting, testing, and documentation steps.

Core Features & Use Cases

  • All-in-one quality gate execution: run lint, tests, and docs checks in sequence.
  • Final verification after parallel sub-agents: confirm nothing was missed during parallelization.
  • Clear, structured status reports including a detailed summary and actionable next steps.

Quick Start

Invoke the quality workflow to run all gates in sequence and report a final status.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I automate code quality checks across linting, testing, and documentation?

Run all quality gates in sequence to automate code quality verification across linting, testing, and documentation. It executes deterministic make commands including check-fix, check, check-strict-all, test-with-coverage, and doc, then aggregates results into a structured status report.

What is the best way to verify code quality after running parallel sub-agents?

Perform a final verification check after parallel sub-agents by running an all-in-one quality gate workflow. It sequentially executes lint, test, and documentation checks to confirm nothing was missed during parallelization, providing a structured status report with actionable next steps.

Do I need a Makefile to run automated quality gates and test coverage?

Yes, the automated quality verification workflow requires a Makefile configured with specific targets. It executes deterministic make commands including check-fix, check, check-strict-all, test-with-coverage, and doc to aggregate code quality results.

Can I run linting and documentation checks alongside tests in a single step?

Yes, you can run linting, testing, and documentation checks in a single sequence. The workflow acts as an all-in-one check by executing make check, make test-with-coverage, and make doc, aggregating all results into one structured status report.

Why does my quality gate workflow report fail even when tests pass?

The quality gate workflow runs multiple checks including strict linting and documentation generation via make check-strict-all and make doc. A failure in any of these gates, not just tests, will result in a failed aggregated status report with actionable next steps.