Test Impact Analysis
From the author
Analyzing code changes to determine which tests are impacted, enabling selective test execution and faster CI feedback loops.
Install
npx skills add PramodDutta/qaskills --skill 'Test Impact Analysis' -a claude-code
Installs to .claude/skills/Test-Impact-Analysis/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 85
Security100
Provenance69
Maintenance100
Licence100
Adoption40
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- test-coveragejmagly/aiwgAnalyze test coverage reports, identify gaps by priority, and recommend test improvements with trend trackingTesting★ 225
- blast-radiusathola/claude-night-marketAnalyzes code change impact with risk scoring and affected-node mapping. Use before merging to understand what a change touches and what lacks test coverage.Testing★ 343
- testingseb1n/awesome-ai-agent-skillsGenerate, execute, and analyze tests for codebases, covering unit, integration, and end-to-end testing with coverage reporting. Use when the user requests testing or provides relevant inputs for this workflow.Testing★ 228
- designing-testsCloudAI-X/claude-workflow-v2Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.Testing★ 1.4K
- experimentationcbrock84/headcountDesigns, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation. Use this to plan a test, judge whether a result is real, build an experimentation program, decide what to test next, or diagnose why tests keep producing inconclusive or non-replicating results.Testing★ 2.1K
- review-testingposit-dev/skillsReview test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.Testing★ 547
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in