agentsclimarketplace

Git bisect debugging

Skill planifest/planifest-framework/planifest-framework/external-skills/git-bisect-debugging

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill git-bisect-debugging

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Locate regression-introducing commits using git bisect with deterministic classification. Use when a reproducible regression exists but the introducing commit is unknown; do not use for CI workflow design or application behavior implementation.

SKILL.md

2.0 KB, as published. Nobody here has run it

Git Bisect Debugging

Overview

Use this skill to isolate first-bad commits quickly and reproducibly, so fixes target root cause instead of symptoms.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Determinism guidance:
    • references/bisect-determinism-guidance.md

Templates And Assets

  • Session log template:
    • assets/bisect-session-log-template.md
  • Verification checklist:
    • assets/bisect-checklist.md

Inputs To Gather

  • Known good commit and known bad commit.
  • Deterministic pass/fail command for classification.
  • Environment requirements for reproducible execution.
  • Evidence expectations for culprit validation.

Deliverables

  • Culprit commit candidate with evidence trail.
  • Bisect session log with classified steps.
  • Confidence statement and next action recommendation.

Workflow

  1. Validate good/bad endpoints and deterministic classifier command.
  2. Run bisect and classify commits consistently.
  3. Capture classifications in assets/bisect-session-log-template.md.
  4. Re-validate candidate culprit around boundary commits.
  5. Close with assets/bisect-checklist.md and next-step recommendation.

Quality Standard

  • Good/bad endpoints are verified before bisect begins.
  • Classification is deterministic and repeatable.
  • Culprit claim is supported by reproducible evidence.
  • Session records are sufficient for peer audit.

Failure Conditions

  • Stop when classification is flaky or environment-dependent.
  • Stop when no reliable good/bad endpoints can be identified.
  • Escalate when interacting commits prevent single-commit isolation.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.