probe-merged-change

Runs exploratory quality testing on merged changes across five quality vectors.

10|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/constructorfabric/insight --skill probe-merged-change-constructorfabric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: probe-merged-change
Source: https://github.com/constructorfabric/insight/tree/main/.claude/skills/probe-merged-change
Command: npx skills add https://github.com/constructorfabric/insight --skill probe-merged-change-constructorfabric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a change merges, the author's own tests have already passed, but nobody has tried to break it. This Skill performs an exploratory quality pass over an already-merged change in constructorfabric/insight, testing the merge description's claims on a stand running that exact build and filing actionable bug reports. ## Core Features & Use Cases - Claim-driven testing: Reads the merge description as testable assertions and drives each one until it breaks, including documented workarounds, stated limits, and end-to-end verification claims. - Five-vector test plan: Executes a plan across Efficiency, Reliability, Performance, Security, and Versatility, probing for silent truncation, combined-limit defects, and client/server contract mismatches. - Disciplined reporting: Files surviving findings through file-bug-insight while filtering out pre-existing platform behavior, environment artifacts, deferred work, and defended design decisions. - Use Case: After a PR adding a capped listing endpoint merges, ask for an exploratory pass on it; the Skill smokes the migration on a pinned-build stand, probes the cap past its limit, and files a report when rows become unreachable. ## Quick Start Run an exploratory quality pass on the change that just merged in PR #142 and file any defects you find.

Frequently Asked Questions about probe-merged-change

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

FAQPage Schema
How do I test a change that has already been merged?

Run an exploratory pass that reads the merge description as testable claims, smokes the migration and a round trip on a stand carrying that exact build, then executes a test plan across five quality vectors and files surviving findings as bug reports.

What is exploratory testing of a merged pull request?

It is a post-merge quality pass that treats the author's stated claims, limits, and workarounds as assertions to break, rather than re-running the author's own test suite. Findings are classified and filed only after reproduction on a healthy stand.

When should I not use post-merge exploratory testing?

Do not use it for planning tests before implementation, writing a Testing section into an issue, validating an entire stand, or confirming a known defect is fixed. Those belong to scoping, authoring, stand-validation, and fix-verification workflows respectively.

Why test on a stand with the exact build instead of local main?

Pinning images to the release build tag and reusing a compose project with existing volumes runs migrations against a populated database, which is the case that actually breaks. A fresh local instance only proves the migration works on empty data.

What findings should not be filed as bugs after exploratory testing?

Exclude pre-existing platform behavior reproduced on untouched endpoints, environment artifacts from the stand, deferred work the change explicitly names, and documented design decisions the author defended. Report passing checks too so readers can judge thoroughness.