inquisitor

Analyze test strategies for coverage gaps, mock fidelity, and flaky patterns.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/benediktms/overmind --skill inquisitor-benediktms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inquisitor
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/inquisitor
Command: npx skills add https://github.com/benediktms/overmind --skill inquisitor-benediktms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate whether test strategies catch regressions by highlighting coverage gaps, mock fidelity issues, pyramid balance, regression risk, and flaky patterns.

Core Features & Use Cases

  • Identifies coverage gaps across branches, error paths, and edge cases not exercised by tests.
  • Assesses test pyramid balance to ensure appropriate distribution of unit/integration/E2E tests.
  • Flags mock fidelity issues where tests pass but do not reflect production behavior.
  • Highlights regression risk and flaky patterns to reduce false confidence.
  • Encourages test independence and negative tests to improve resilience.

Quick Start

Describe the PR changes and ask inquisitor to assess test strategy, coverage gaps, and mock fidelity.

Frequently Asked Questions about inquisitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate if my test strategy catches regressions effectively?

Evaluate regression test strategies by analyzing code changes and PRs to highlight coverage gaps, mock fidelity issues, and flaky patterns. This process generates a structured gap-and-risk report with recommended fixes to ensure tests catch regressions effectively.

Why do my tests pass but still miss production regressions?

Tests pass but miss regressions due to mock fidelity issues where tests overfit to mocks and fail to reflect production behavior. Evaluating test independence and negative tests helps identify these regression risks and reduce false confidence in the test suite.

What is the best way to find coverage gaps in error paths and edge cases?

The best way to find coverage gaps is to analyze test strategies across branches, error paths, and edge cases not exercised by tests. This identifies areas where tests might miss regressions and generates a structured gap-and-risk report with targeted recommended fixes.

How do I check my test pyramid balance for unit, integration, and E2E tests?

Check test pyramid balance by assessing the distribution of unit, integration, and E2E tests across a project. This ensures appropriate coverage allocation and highlights regression risks or flaky patterns that reduce overall test suite resilience.

Can I assess mock fidelity issues for a specific PR?

Yes, you can assess mock fidelity for a specific PR by describing the PR changes and requesting a test strategy evaluation. This flags where tests pass but do not reflect production behavior and generates a structured gap-and-risk report with recommended fixes.

When should I not rely on my current test coverage for regression detection?

Do not rely on current test coverage when flaky patterns exist, tests overfit to mocks, or negative tests are missing. Evaluating test independence and pyramid balance helps highlight these regression risks and reduce false confidence in the test suite.