Skip to content
TrustedSkillsbeta
Back to all skills

Systematic Debugging

Checked
johnkmcleod9·vlatest·testing·MIT

Systematically identifies and resolves code errors through methodical analysis and targeted fixes for improved reliability.

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 johnkmcleod9/antigravity-skills-workflows --skill systematic-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

johnkmcleod9

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 johnkmcleod9/antigravity-skills-workflows at d3a39016b3.

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

Commit
d3a39016b3
Manifest
.agent/skills/systematic-debugging/SKILL.md
Scanned
11 files, 1,218 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

This skill facilitates systematic debugging of code or processes. It helps identify the root cause of issues by guiding you through a structured approach, including isolating variables and testing hypotheses. The skill aims to improve efficiency in troubleshooting and reduce time spent on resolving errors.

When to use it

  • You're facing an unexpected error in your code and need help pinpointing the source.
  • A process is failing intermittently, and you want a methodical way to diagnose the problem.
  • You are trying to understand why a complex system isn’t behaving as expected.
  • You want to improve your debugging skills by following a structured approach.

Key capabilities

  • Structured Debugging Process
  • Variable Isolation
  • Hypothesis Testing
  • Root Cause Identification

Example prompts

  • "I'm getting an error 'TypeError: undefined is not a function'. Can you help me debug this code?"
  • "My data pipeline is failing occasionally. Walk me through a systematic debugging process."
  • "I suspect the issue lies in the authentication module. How can I isolate and test that component?"

Tips & gotchas

The skill assumes some familiarity with the codebase or system being debugged. It's most effective when you have access to logs, error messages, and relevant code snippets.