qa-checklist

Automate six-phase QA checks for code changes before merging and deploying.

38|5|Updated Dec 18, 2025

Search Tags:#deployment #qa #quality-assurance #build-verification #test-suite #region-check #no-touch-zones

Ready to run

npx skills add https://github.com/Svenja-dev/claude-code-skills --skill qa-checklist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-checklist
Source: https://github.com/Svenja-dev/claude-code-skills/tree/main/skills/qa-checklist
Command: npx skills add https://github.com/Svenja-dev/claude-code-skills --skill qa-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a formal, repeatable quality assurance checklist to prevent regressions and deployment issues by validating code changes through structured phases before merges and releases.

Core Features & Use Cases

6-Phase QA pipeline: Build Verification, Test Suite, No-Touch Zones, Region Check, Security Review, and QA Report generation.
Triggers on common workflows: git commits, deployment commands, and the /qa prompt to automate checks.
Use Case: ensure production readiness by halting deployments on failures and generating a centralized QA report for compliance and audits.

Quick Start

Copy the skill to ~/.claude/skills/qa-checklist/ and invoke QA via /qa or during pre-deploy checks. Configure no-touch zones and region controls in your CLAUDE.md.

Frequently Asked Questions about qa-checklist

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

FAQPage Schema

How do I automate quality assurance checks before a production deployment?▼

Automate quality assurance checks by triggering a 6-phase pipeline covering build verification, test suites, and security reviews to halt deployments on failures. This prevents regressions by validating code changes through structured phases before merges and releases.

What is a no-touch zone in a deployment QA pipeline?▼

A no-touch zone in a deployment QA pipeline is a configurable restricted area in your repository that triggers a failure if modified. It prevents unauthorized code changes to critical paths by enforcing region checks and security reviews before merging.

How do I run a pre-merge build verification and test suite check?▼

Run pre-merge build verification and test suite checks by invoking the QA prompt during git commits or pre-deploy commands. This executes the automated checklist to validate builds, run tests, and generate a centralized QA report for compliance.

Can I configure region targets and security scans for my deployment pipeline?▼

Yes, you can configure region targets and security scans by defining controls in your repository configuration. The pipeline enforces region checks and security reviews to ensure production readiness before any code merge or release deployment.

How do I generate a centralized QA report for compliance and audits?▼

Generate a centralized QA report for compliance by running the automated quality assurance phases during your release workflow. The pipeline validates commits, PRs, and deployment commands, outputting a formal report detailing build, test, and security results.

Why do I need a formal QA checklist for software deployment?▼

You need a formal QA checklist for software deployment to prevent regressions and deployment issues through repeatable validation. It enforces structured phases including build verification and security reviews to halt deployments on failures and ensure production readiness.