skills.rest
patrickrmoore
patrickrmooreCOMMUNITY
Explore all skills by this author →
GitHub

quality-control

Automate end-to-end quality control checks across a feature lifecycle.

Updated Mar 22, 2026
Search Tags:#testing#security#qa#traceability#static-analysis#quality-control#bug-tracking
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill quality-control-patrickrmoore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-control
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/quality-control
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill quality-control-patrickrmoore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes automated, end-to-end quality control checks to ensure features meet requirements, tests succeed, and issues are surfaced early.

Core Features & Use Cases

  • Context checks validate prerequisites and milestones.
  • Static analysis, tests, and security scans verify quality and safety.
  • Bug-task generation feeds issues back into the implementation loop when checks fail.

Quick Start

Run QC on the current feature by executing the QC workflow for the feature directory.

Frequently Asked Questions about quality-control

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

FAQPage Schema
How do I automate quality control checks across a feature's lifecycle?▼

Automated quality control checks validate feature prerequisites, run static analysis and tests, execute security scans, and generate bug tasks for failures. Results are recorded in a qc-report.md file to ensure code quality throughout the feature lifecycle.

How does automated bug tracking work when static analysis or tests fail?▼

Automated bug tracking generates actionable bug tasks and appends them directly to tasks.md when quality control checks fail. This feeds issues back into the implementation loop, ensuring failures are tracked and resolved within the feature directory.

What files do I need in my feature directory to run end-to-end QC checks?▼

End-to-end QC checks require plan.md, spec.md, tasks.md, and project-instructions.md in the feature directory. The workflow reads these artifacts to validate context, enforce conventions, and execute static analysis and security scans.

Can I use automated QC checks to enforce traceability between specs and tests?▼

Yes, automated QC checks enforce artifact conventions and validate milestones by reading plan.md and spec.md. This traceability ensures features meet requirements, tests succeed, and static analysis passes before recording results in qc-report.md.

What's the best way to integrate security scans into an automated QA workflow?▼

Integrating security scans into an automated QA workflow executes them alongside static analysis and tests during feature validation. When security issues surface, the workflow generates actionable bug tasks appended to tasks.md for immediate resolution.

Why are my quality control checks failing during autopilot scenarios?▼

Quality control checks fail during autopilot scenarios when prerequisites, milestones, or artifact conventions are not met. The workflow handles these scenarios by reporting failures and appending actionable bug tasks to tasks.md for tracking and resolution.

Related Skills

Explore More Software Engineering Skills→
patrickrmoorepatrickrmoore

implement-qc-loop

Automates iterative Implement and QC loops with artifact validation and guardrails.

Community
Advanced
hungthinh04hungthinh04

requesting-code-review

Verify staged git changes with security scans, tests, linting, and review.

Community
Advanced
ReefBytes-OwnerReefBytes-Owner
1

verify

Run lint, test, and security checks in parallel and generate a consolidated report.

Community
Advanced
RedHatProductSecurityRedHatProductSecurity
47

sarif-parsing

Parse, filter, aggregate, and validate SARIF static analysis reports.

Official
Intermediate