Automate six-phase QA checks for code changes before merging and deploying.
npx skills add https://github.com/Svenja-dev/claude-code-skills --skill qa-checklist
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
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.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
daffy0208Automate QA with test pyramids, code-quality checks, and phase-transition gates.
CODE-SAURABHMerge approved pull requests and verify production health after deployment.
spallempatiEnforce mandatory peer review and automated quality gates on pull requests.
UnaMentisRun linting and tests for Swift and Python before committing.
