Analyze code diffs to identify test coverage gaps and produce JSON findings.
npx skills add https://github.com/xbpk3t/ce-codex --skill testing-reviewer
Please help me install this Agent Skill. Skill: testing-reviewer Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/testing-reviewer Command: npx skills add https://github.com/xbpk3t/ce-codex --skill testing-reviewer
This Skill helps reviewers determine whether tests in a code diff actually validate behavior and catch regressions rather than merely existing. It surfaces false confidence caused by weak assertions, implementation-coupled checks, and missing error-path coverage so reviewers can prioritize meaningful tests.
Ask the testing-reviewer to analyze the pull request diff and return JSON findings listing untested branches, weak or brittle tests, and residual risks with confidence indicators.
High-intent search queries and answers about installing and using this skill.
To detect untested branches in a pull request diff, apply test coverage analysis to the changes to identify untested branches and missing error-path coverage. This surfaces false confidence caused by weak assertions and implementation-coupled checks.
Vacuous assertions in unit tests are weak checks that validate mocks or truthiness instead of real outputs. You identify them by analyzing test changes to flag tests that only check for no-throw execution, ensuring tests actually validate behavior.
Finding brittle implementation-coupled tests during code review involves analyzing assertions and snapshots that break during refactoring without actual behavior changes. Flagging these tests helps prioritize meaningful tests that validate outcomes rather than internal structure.
You can automate test quality checks in CI by analyzing pull request diffs to detect missing error-path coverage and vacuous assertions. The process outputs JSON-formatted findings enumerating testing gaps and residual risks suitable for CI gating.
You assess residual risks and confidence in unit test coverage by evaluating code diffs for untested branches and weak assertions. This generates JSON-formatted findings enumerating specific testing gaps alongside confidence indicators for code review.
nilleReview code diffs for correctness, security, and conventions.
OneKeyHQReview pull request diffs for security risks and vulnerabilities.
korchasaAutomate final pull request review and merge in an SDLC pipeline.
jmaglyAnalyze lcov, cobertura, and istanbul coverage reports to identify gaps and recommend prioritized tests.
