- Home
- Skills
- Testing & Debugging
- RegressionTrail — Git Bug Origin Investigator
More screenshots
Works with the AI Agents you already use
RegressionTrail — Git Bug Origin Investigator
Trace suspected regressions across renames, reverts and Git history with reproducible evidence.
$5
RegressionTrail — Git Bug Origin Investigator
Example session with this skill installed
Run RegressionTrail — Git Bug Origin Investigator as an evidence-first preflight. This is a representative, hypothetical test case: A discount calculation starts rounding twice after a refactor; git blame points to formatting. The materials I have available are: reproduction steps or failing test; repository and revision range; relevant error logs. Tell me what is evidenced, what is missing, which claims must be held, the exact corrections, and a clean verification plan. Do not claim you opened a file or performed a live run unless one is actually supplied.
- Read your context and instructions
- Compiled the regressiontrail
REPRESENTATIVE EXAMPLE — NOT A LIVE RUN
PREFLIGHT: HOLD / VERIFY BEFORE ACTING. Task: Trace suspected regressions across renames, reverts and Git history with reproducible evidence.
Scenario supplied by buyer: A discount calculation starts rounding twice after a refactor; git blame points to formatting.
-
MATERIAL FINDING (HIGH): Formatting attribution does not establish the functional regression source. The case describes a potential issue; no underlying account, file or production service has been accessed by this illustrative demo.
-
TRACEABILITY MATRIX
- Claimed behavior: A discount calculation starts rounding twice after a refactor; git blame points to formatting.
- Critical evidence sources: reproduction steps or failing test, repository and revision range, relevant error logs.
- Status: NOT VERIFIED from primary artifacts in this example. A real invocation must attach the files or authorize a read-only source inspection and record exact references.
- CHECKS THE SKILL WILL RUN
- Define an observable failing behavior and identify a last-known-good point when possible.
- Trace code through renames with git log --follow and search historical text additions.
- Use read-only blame and candidate diffs before suggesting targeted bisect.
- Differentiate correlation from proven cause; include commit hashes and failing test evidence.
- Return smallest safe fix strategy, retest and rollback notes without changing branches automatically.
-
CORRECTION TO PROPOSE
Search history around the rounding helper; build a two-value regression fixture and bisect only with a deterministic test. Do not present this as implemented until the seller/developer actually applies the change and reviews the result. -
REPRODUCTION / ACCEPTANCE TEST
Re-run the fixture at the suspected bad and previous good revisions. Capture the before/after witness (paths, commands, timestamp, observed outcome), distinguish a script signal from a working end-to-end product, and do not invent a PASS. -
SCOPE LIMIT
Without repository history or a reliable failing test the verdict remains an investigation hypothesis.
Final handoff: a clear evidence-linked issue list, copy-ready proposed changes where appropriate, a prioritized checklist, and a statement of exactly which tests were and were not run.
Connects securely to your tools. The creator never sees your data.
About this skill
RegressionTrail — Git Bug Origin Investigator
Trace suspected regressions across renames, reverts and Git history with reproducible evidence.
What you receive
- A ready-to-install skill with a repeatable, evidence-first procedure.
- A source-to-claim discrepancy matrix, severity tags and specific corrective actions.
- A clearly separated verification checklist and unknowns register.
- A representative worked example; it is not passed off as a live customer run.
Example issue
A discount calculation starts rounding twice after a refactor; git blame points to formatting.
Trust boundary
Without repository history or a reliable failing test the verdict remains an investigation hypothesis.
No paid API subscription is bundled. The agent can inspect materials supplied by the buyer in its supported environment. Access to private services is never presumed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Without repository history or a reliable failing test the verdict remains an investigation hypothesis.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Permissions
File Scopes
No production changes or account access without owner authorization.