qa-check

Automate the full QA pipeline using repository QA documentation and tool rules.

3|Updated Mar 1, 2010

Search Tags:#automation #security #qa #pipeline #pre-commit #quality-assurance #ci

Ready to run

npx skills add https://github.com/harleypig/dotfiles --skill qa-check-harleypig

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-check
Source: https://github.com/harleypig/dotfiles/tree/main/config/claude/skills/qa-check
Command: npx skills add https://github.com/harleypig/dotfiles --skill qa-check-harleypig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA checks in software projects are often manual, fragmented, and inconsistent. This skill automates the full quality-assurance pipeline by orchestrating the repo's QA rules, reducing drift and speeding PR readiness.

Core Features & Use Cases

Tool-agnostic orchestration: reads the repo's QA documentation (qa.md, RULES) to determine applicable checks and runs them in a defined sequence.
Comprehensive coverage: coordinates lint, tests, security scans, formatting, and CI checks across languages and tooling.
Reporting: generates a consolidated status report detailing active, planned, or missing dimensions and actionable remediation steps.

Quick Start

Run the QA pipeline against the current repository to validate code quality, tests, security, and CI readiness.

Frequently Asked Questions about qa-check

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

FAQPage Schema

How do I automate the full QA pipeline for a codebase?▼

Automate the full QA pipeline by orchestrating repo QA documentation and tool rules to run lint, tests, and security scans in a defined sequence. This coordinates checks across languages and CI workflows to reduce drift and speed PR readiness.

What is the best way to coordinate pre-commit and CI checks across multiple languages?▼

Coordinate pre-commit and CI checks across multiple languages by reading qa.md and per-tool rules to determine applicable checks. This tool-agnostic orchestration enforces formatting and runs commands in a unified sequence.

Do I need a QA document to run automated quality-assurance checks?▼

A QA document is required to run automated quality-assurance checks. The pipeline applies to repositories with a qa.md file and tool rules, using them to determine applicable checks and coordinate commands.

How does automated QA reporting handle missing checks or tooling?▼

Automated QA reporting handles missing checks by generating a consolidated status report. This report details active, planned, or missing dimensions and provides actionable remediation steps for the codebase.

Can I use this to enforce formatting and security scans before a pull request?▼

You can enforce formatting and security scans before a pull request by running the full quality-assurance pipeline. It coordinates these checks across your repo's tooling to validate CI readiness and produce a status report.

Why should I use tool-agnostic QA orchestration instead of individual pre-commit hooks?▼

Tool-agnostic QA orchestration centralizes fragmented checks into a single pipeline, reducing drift and inconsistency. It reads your existing qa.md and per-tool rules to coordinate commands across languages, providing a consolidated report individual hooks lack.