Skip to content
TrustedSkillsbeta
Back to all skills

Git Bisect Debugging

Checked
sjungling·vlatest·backend·MIT

Helps with Git, debugging as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sjungling/sjungling-claude-plugins --skill git-bisect-debugging -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sjungling

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned sjungling/claude-plugins at 0dd093bc8c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0dd093bc8c
Manifest
plugins/git-tools/skills/git-bisect-debugging/SKILL.md
Scanned
4 files, 350 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The git-bisect-debugging skill automates the process of using git bisect to identify the commit that introduced a bug. It helps narrow down problematic commits by systematically testing changes, significantly reducing debugging time compared to manual inspection. The tool guides you through marking commits as good or bad until the faulty commit is isolated.

When to use it

  • You've identified a regression in your codebase and need to quickly pinpoint the responsible commit.
  • A bug report points to a specific feature, but the exact cause isn’t immediately obvious.
  • You are working on a large project with frequent commits and want an efficient way to isolate bugs.
  • When you suspect a recent change introduced a bug, but aren't sure which one.

Key capabilities

  • Automated git bisect execution.
  • Guidance through the "good/bad" commit marking process.
  • Isolation of the faulty commit that introduced the bug.
  • Reduces debugging time compared to manual inspection.

Example prompts

  • “Run git bisect to find the commit that caused this bug.”
  • “Bisect between commit A and commit B, marking [commit hash] as bad.”
  • "Start a bisect session to identify the regression introduced in version 1.2."

Tips & gotchas

  • Requires a Git repository with a clear "good" (working) and "bad" (broken) state.
  • The accuracy of git bisect depends on having reliable tests or methods for determining if a commit is good or bad.