cc-quality-practices

Automate QA practices with structured code reviews, test-case design, and debugging workflows.

351|31|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/ryanthedev/code-foundations --skill cc-quality-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-quality-practices
Source: https://github.com/ryanthedev/code-foundations/tree/main/skills/cc-quality-practices
Command: npx skills add https://github.com/ryanthedev/code-foundations --skill cc-quality-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to quality assurance, enabling teams to systematically detect and prevent defects through codified checklists, QA gates, and robust debugging practices.

Core Features & Use Cases

  • CHECKER mode audits QA practices with evidence tables and standardized defect reporting.
  • APPLIER mode generates test cases (5:1 dirty-to-clean ratio), runs the Scientific Debugging Method (STABILIZE-HYPOTHESIZE-EXPERIMENT-FIX-VERIFY-SEARCH), and sets up inspection procedures.
  • Use this Skill when planning QA, choosing review methods, designing tests, or debugging failures across both team-based and solo contexts.

Quick Start

Run a quality-assurance session on the latest change: start CHECKER to audit QA practices, or switch to APPLIER to generate tests and debugging plans.

Frequently Asked Questions about cc-quality-practices

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

FAQPage Schema
How do I implement structured code review and QA gates for my team?

Structured code review and QA gates are implemented by standardizing defect reporting and codifying inspection procedures. You can automate these quality assurance practices to systematically detect and prevent defects across team-based contexts.

What is the best way to design test cases with a high defect detection rate?

The best way to design test cases for high defect detection is using a 5:1 dirty-to-clean test ratio. This strategy prioritizes negative and edge-case testing to ensure robust software reliability before deployment.

How does scientific debugging work for diagnosing software failures?

Scientific debugging works by following a structured workflow: STABILIZE, HYPOTHESIZE, EXPERIMENT, FIX, VERIFY, and SEARCH. This evidence-based method systematically diagnoses defects and ensures post-fix verification prevents regressions.

Can I use this QA checklist approach for solo development workflows?

Yes, you can use this QA checklist approach for solo development workflows. The quality assurance practices, test-case design, and debugging workflows are explicitly designed to function across both team-based and solo contexts.

What is a CHECKER mode audit in quality assurance?

A CHECKER mode audit evaluates existing quality assurance practices using evidence tables and standardized defect reporting. It systematically reviews your preparation and inspection processes to identify gaps in software reliability.