- Home
- Skills
- Code Quality & Review
- Git regression evidence timeline
Git regression evidence timeline
For software maintainers: an evidence timeline and discriminating investigation plan.
$12
Works with the AI Agents you already use
Git regression evidence timeline
Example session with this skill installed
Use the skill to produce an evidence timeline and discriminating investigation plan. Input S1: Commit A passes checkout test. B changes timeout. C changes README. Test at C fails; B was not tested.
- Read your context and instructions
- Compiled the git regression evidence
Synthetic test example. Recorded AI smoke-test response. No real service changes were executed.
C is the first observed failing revision in S1, not a proven first bad commit. B is a plausible candidate because it changes timeout; its test result is unknown.
Evidence timeline in the supplied A/B/C order:
- A: checkout test passes.
- B: timeout change; untested.
- C: README change; checkout test fails.
Parent relations and timestamps are not provided, so this is the narrated order rather than independently verified ancestry. A README-only change seems less directly connected, but other changes, configuration and intermittent failures are not excluded.
Proposed investigation: obtain parent relations and exact test/environment details; reproduce A and C with the same checkout fixture, dependencies and configuration; test B under that same setup. If A passes and B fails reproducibly, inspect the timeout diff and compare measured request timing. If B passes and C fails, inspect the full B-to-C difference and environment rather than assuming the README caused it. For a larger confirmed ancestry window, use a disposable comparison/bisect process without rewriting history.
Missing inputs: diffs, ancestry, reproducible failure details and environment parity.
Acceptance check: identify the smallest repeatable passing/failing revision pair with captured output before assigning a first bad commit. No Git commands or tests were executed.
Connects securely to your tools. The creator never sees your data.
About this skill
Use this skill when you have supplied commit excerpts, test observations and a regression window and need an evidence timeline and discriminating investigation plan.
The workflow:
- Order commit IDs by supplied parent relations or timestamps without inventing history.
- Separate first observed failure from first bad commit.
- Identify candidate changes affecting the failing behavior and competing explanations.
- Specify a reproducible comparison or bisect plan without modifying history.
You receive the work product with input-linked findings, visible unknowns and concrete verification checks. Work from pasted or redacted text. This skill does not execute changes, send messages or access service accounts.
Original AI-assisted content. A synthetic worked example is included. Use through your Agensi-connected agent. No extra paid API or runtime is required for this workflow. Delivery is through the Agensi agent connection. No sales, ranking or compliance outcome is promised.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
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
No special permissions declared or detected