Analyze test suites for coverage gaps, assertion quality, and false-confidence patterns.
npx skills add https://github.com/zivtech/joyus-desktop --skill qa-critic
Please help me install this Agent Skill. Skill: qa-critic Source: https://github.com/zivtech/joyus-desktop/tree/main/.claude/skills/qa-critic Command: npx skills add https://github.com/zivtech/joyus-desktop --skill qa-critic
This skill addresses the danger of false confidence in software testing, where a green build might hide critical failures due to weak assertions, happy-path bias, or flaky tests.
Ask the qa-critic to review the current test suite in the repository to identify potential coverage gaps and reliability risks.
High-intent search queries and answers about installing and using this skill.
To audit a test suite for coverage gaps, you evaluate test source code, configuration files, and CI settings to identify weak assertions, happy-path bias, and false-confidence patterns. This risk-based assessment ensures your green CI signal reflects reliable verification.
A green CI build hides critical failures due to false-confidence patterns like weak assertions, happy-path bias, or flaky tests. Analyzing your test suite helps map these risks and identifies where verification fails to protect against meaningful product failures.
The best way to analyze CI stability before a major release is performing a comprehensive risk-based assessment of your test suite. This involves evaluating assertion quality and coverage gaps to ensure the green signal represents a safe and reliable product state.
Yes, you need access to test source code, configuration files, and CI settings to perform test strategy validation. Accessing these inputs allows a comprehensive evaluation of reliability risks and false-confidence patterns within your verification process.
You need to assess test suite reliability for risk mapping when you want to identify where your tests fail to protect against meaningful system failures. This process evaluates assertion quality and coverage gaps to eliminate false confidence before pre-release audits.
TheycallmehollaMap test coverage against module risk levels to produce a prioritized testing report.
joshsymondsAudit test suites and categorize tests as RED, YELLOW, or GREEN.
veilkeyAutomate testing, static analysis, and building for Go projects.
wshaddixAnalyze .NET code for CRAP scores and generate coverage reports.
