dsh-test-insight

Before every merge, the most common question is: which tests should this change actually add, and where are the protection gaps? dsh-test-insight turns that guesswork into an evidence-backed workflow. It reads the repository test-to-source mapping, weighs change risk, and produces a structured TEST-PLAN.md plus an isolated, review-only set of test drafts. Every finding carries an evidence level (fact, inference, suggestion, or needs-confirmation), so reviewers can instantly separate hard evidence from items that still require human judgment.

Three capabilities do the heavy lifting. First, gap detection pinpoints which modules and entry points lack corresponding test coverage. Second, risk ranking in change mode takes a specific diff or working-tree change and orders the test targets you should prioritize. Third, a target-by-category coverage matrix surfaces structural blind spots that a single aggregate number would hide. The entire pipeline is read-only by default: it never runs the target repo tests, builds, lint, or type-check. Executing tests requires both an explicit execute-tests flag and a whitelisted test-command (dual authorization). Drafts are always marked DRAFT ONLY; passing a syntax check is not the same as passing the tests.

It fits small teams that need a repeatable test-planning step in their merge process, as well as engineers who want to turn the what-tests-should-we-write conversation into a traceable document. Use it as a DSH plugin inside an agent workflow, or drop the standalone CLI and library into an existing CI pipeline.