Prepare-regression takes a PR URL, or a repository plus a commit or range, and works out the complete change as two states, S0 before and S1 after. It handles unmerged pull requests, merge commits, squash merges and rebased series, and blocks when a range is ambiguous or a root baseline is missing.
The agent freezes commit messages or the PR title, body, discussion, reviews and inline comments with URLs and collection time, locates security and threat-model documents, exports the sources with a snapshot script, and seals a preparation record.
What You Get
- A sealed prepare.json with boundary explanations, frozen context and source artifacts
- Frozen S0 and S1 source exports in a new directory
- Collected PR or commit discussion with URLs, collection time, limits and lifecycle
- Paths to security or threat-model documents in both states, or notes on search limits
- A short report back with the selected S0 and S1 and collection limitations
Common Use Cases
- Starting a regression investigation on a merged pull request
- Freezing an unmerged PR at its current head before review
- Preparing a commit range for a release audit
What Makes It Unique
A merged status does not define the change boundary here. The skill spells out how to pin S0 and S1 for each way a PR can land, blocks on ambiguous ranges, and records what could not be collected so that later stages know the limits.
Under The Hood
The agent reads SKILL.md plus a regression definition and a file contract. It calls PR and commit APIs, paginated, to collect discussion, runs a bundled Python snapshot script through uv with Git to export both states into a new directory, and writes and seals a JSON record there. It reads project guidance files once the target commit is known and treats them as data. It runs no target code and makes no changes to the repository.