skills/qa-checklist/SKILL.md
Formal Quality Assurance Checklist before every Merge/Deploy. 6-phase validation with Build Verification, Test Suite, No-Touch Zones, Region Check, Security Review, and QA Report generation. Activate on "merge", "deploy", "release", "production", or /qa command.
npx skillsauth add svenja-dev/claude-code-skills qa-checklistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Formal Quality Assurance Checklist before every Merge/Deploy
This skill activates automatically on:
git commit (after production code changes)vercel --prod, npm run deploy, etc.)/qa commandCustomize these values for your project:
# Add to your project's CLAUDE.md or settings
no_touch_zones:
- "src/auth/**" # Authentication logic
- "src/core/**" # Core business logic
- "config/production.*" # Production config
required_region: "your-region" # e.g., fra1, us-east-1
deploy_timeout: 60 # seconds
npx tsc --noEmit
Expected: No errors
| Status | Action | |--------|--------| | PASS | Continue to 1.2 | | FAIL | STOP - Fix type errors |
npm run build
Expected: Build successful, no warnings
| Status | Action | |--------|--------| | PASS | Continue to Phase 2 | | FAIL | STOP - Fix build errors |
npm run test
Expected: All tests green
npm run test:e2e
Expected: Critical flows working
Check if protected files were modified:
# Replace with your no-touch zones
git diff --name-only HEAD~1 | grep -E "(auth|core|production)"
Expected: No matches (or explicit approval present)
| File Pattern | Modification Allowed? |
|--------------|----------------------|
| **/auth/** | ONLY with explicit request |
| **/core/** | ONLY with explicit request |
| config/production.* | ONLY with explicit request |
Verify deployment target matches requirements:
# Vercel example
npx vercel inspect <preview-url> --wait
# AWS example
aws configure get region
# Check environment
echo $NODE_ENV
Expected: Correct region/environment
# Verify production deployment
curl -s -o /dev/null -w "%{http_code}" https://your-domain.com/health
Expected: 200 OK
git diff HEAD~1 | grep -iE "(password|secret|api_key|token|private_key)" | grep -v "process\.env\|\.env\|example"
Expected: No matches
# TypeScript: Check for untyped any
git diff HEAD~1 --name-only -- "*.ts" "*.tsx" | xargs grep -l ": any" 2>/dev/null
Expected: No new any types (or documented reason)
npm audit --production
Expected: No high/critical vulnerabilities
After completing all checks, generate a report:
## QA Validation Report
**Date:** [ISO Timestamp]
**Branch:** [Branch Name]
**Commit:** [Commit Hash]
### Results
| Check | Status | Details |
|-------|--------|---------|
| TypeScript | PASS/FAIL | [Error count] |
| Build | PASS/FAIL | [Build time] |
| Unit Tests | PASS/FAIL | [X/Y passed] |
| E2E Tests | PASS/FAIL/SKIP | [X/Y passed] |
| No-Touch Zones | PASS/FAIL | [Affected files] |
| Region | PASS/FAIL/N/A | [Current region] |
| Security | PASS/WARN | [Issues found] |
### Verdict
**Status:** APPROVED / REJECTED
**Next Steps:**
- [If APPROVED: Merge/Deploy allowed]
- [If REJECTED: List of issues to fix]
1. Run checks
2. On failure: Implement fix
3. Return to step 1
4. After 3 iterations: Escalate to user
Originally developed for fabrikIQ - AI-powered manufacturing data analysis.
MIT - Free to use and modify
development
Protects design and theme files from unintended changes. Locks tailwind.config, global CSS, and theme variables. Requires explicit confirmation before modifying UI components. Activate on changes to CSS, theme config, or layout components.
tools
Proactive token budget assessment and task chunking strategy. Use this skill when queries involve multiple large file uploads, requests for comprehensive multi-document analysis, complex multi-step workflows with heavy research (10+ tool calls), phrases like "complete analysis", "full audit", "thorough review", "deep dive", or tasks combining extensive research with large output artifacts. This skill helps assess token consumption risk early and recommend chunking strategies before beginning work.
development
Erzwingt striktes Test-Driven Development mit Red-Green-Refactor Zyklus. Blockiert Code-Generierung ohne vorherige Tests. Dokumentiert 13 ungueltige Rationalisierungen. Aktivieren bei neuen Features, Bug Fixes, Refactoring.
development
Enforces TypeScript best practices when writing code. Automatically enables strict typing for TypeScript projects, prevents `any` usage, and recommends generic constraints. Activate on TS/TSX files, new features, code reviews.