qa-changes
Understand and suggest QA test cases based on code changes
When & Why to Use This Skill
The QA Changes Analyser is a specialized Claude skill designed to bridge the gap between development and quality assurance. By intelligently analyzing code diffs, pull requests, and commits, it identifies high-risk areas and suggests targeted QA test cases. This tool ensures that every code modification is backed by a robust testing strategy, helping teams maintain high software quality and prevent regressions during the development lifecycle.
Use Cases
- Pull Request Reviews: Automatically generate a list of recommended test cases for a PR to help reviewers and authors ensure all edge cases are covered before merging.
- Regression Testing Optimization: Identify which specific components are impacted by recent changes to focus testing efforts on the most critical areas, saving time and resources.
- Test Gap Analysis: Compare new code logic against existing test suites to detect uncovered paths and suggest modifications to improve overall test coverage.
- Continuous Integration: Integrate into the CI/CD pipeline to provide developers with immediate feedback on testing requirements for their latest commits.
| name | qa-changes |
|---|---|
| description | Understand and suggest QA test cases based on code changes |
QA Changes Analyser
This skill provides the ability to analyze code changes and suggest relevant QA test cases to ensure software quality. Specially to be used with the qa-use toolkit (MCP, other skills, subagents, etc).
Instructions
You should:
- Analyze the provided code changes (diffs, pull requests, commits, etc).
- Identify areas that may require QA testing based on the changes.
- Check previously generated QA test cases to see if they cover the new changes.
- Suggest new QA test cases or modifications to existing ones to cover the changes effectively.
Examples
TODO