Agent skill

Debug

by nth5693 in nth5693/gemini-kit

Systematic debugging with structured reproduction and root cause analysis.

MITAuto-check passedDevelopment

Install Debug

skills CLI
$ npx skills add nth5693/gemini-kit --skill debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nth5693/gemini-kit debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nth5693/gemini-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/debug .claude/skills/debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debug
GitHub stars
372
Token cost
~301 tokens
SKILL.md length
116 words
Files
3
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Systematic debugging with structured reproduction and root cause analysis.

  • Works in 4 steps: Reproduce an issue →… → Find Root Cause →… → Create Bug Report →… → …
  • Tasks that involve Debugging
  • SKILL.md covers Overview, When To Use, Instrumentation and What do you want to do?, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Debug is an agent skill from nth5693/gemini-kit. Systematic debugging with structured reproduction and root cause analysis.

Its SKILL.md is about 300 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `templates/bug-report.template.md` and `workflows/reproduce-issue.md`).

It sits in Development, covering Debugging and Root cause analysis. The repository describes itself as: 🚀 19 AI Agents + 44 Commands for Gemini CLI - Code 10x faster with auto planning, testing, review & security. The licence is MIT.

When your agent uses it

  • Tasks that involve Debugging
  • Tasks that involve Root cause analysis

Example prompts

  • “/debug”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Reproduce an issue → workflows/reproduce-issue.md
  2. Find Root Cause → workflows/root-cause-analysis.md
  3. Create Bug Report → templates/bug-report.template.md
  4. Research Error Messages → references/common-errors.md

What it can do on your machine

Read from SKILL.md and the folder at commit f3db206. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debug loads about 301 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 116 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~301

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nth5693/gemini-kit at commit f3db206, republished under its MIT licence (© nth5693). 116 words, ~301 tokens.

Download SKILL.mdSave it as .claude/skills/debug/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
debug
description
Systematic debugging with structured reproduction and root cause analysis.
last_updated
2025-12-20

Debug Skill

Overview

Don't guess; verify. This skill guides you through the systematic process of identifying, reproducing, and fixing bugs.

When To Use

  • Users report a bug
  • You encounter an unexpected error
  • Tests are failing inexplicably

Instrumentation

bash
# Log usage when using this skill
./scripts/log-skill.sh "debug" "manual" "$$"

What do you want to do?

  1. Reproduce an issue → workflows/reproduce-issue.md
  2. Find Root Cause → workflows/root-cause-analysis.md
  3. Create Bug Report → templates/bug-report.template.md
  4. Research Error Messages → references/common-errors.md

The Golden Rule of Debugging

"If you haven't reproduced it, you haven't fixed it."

Always implement a reproduction case (test or script) BEFORE attempting a fix. Highly recommended to use the template at docs/templates/repro-script-template.sh and store artifacts in scripts/repro/.

[!NOTE] No top-level debug/ folder exists. Use skills/debug/ for guidance and scripts/repro/ for artifacts.

© nth5693, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/debug of nth5693/gemini-kit.

  • SKILL.md
  • templates/bug-report.template.md
  • workflows/reproduce-issue.md

Open the folder on GitHubat commit f3db206

Compare with similar skills

Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debug this skillnth5693/gemini-kit372—~301Automated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Graph-Based Bug Tracingtirth8205/code-review-graph32k1 repos~287Automated safety check: PassMIT
Systematic DebuggingChrisWiles/claude-code-showcase6.1k3 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes
  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated 8 days ago
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed
  • Systematic Debugging

    ChrisWiles/claude-code-showcase

    Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.

    6.1k GitHub starsUsed in 3 repos~1.2k tokens
    DevelopmentAuto-check passed
  • Debugging and Error Recovery

    addyosmani/agent-skills

    Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.

    103k GitHub starsUsed in 1 repo~2.6k tokens
    DevelopmentAuto-check passed

More from nth5693/gemini-kit

  • Compound Docs

    nth5693/gemini-kit

    Document solved problems for knowledge persistence. An agent skill from nth5693/gemini-kit.

    372 GitHub stars~760 tokensUpdated 7 mo ago
    Auto-check passed
  • File Todos

    nth5693/gemini-kit

    Manage file-based todo tracking in the todos/ directory. An agent skill from nth5693/gemini-kit.

    372 GitHub stars~432 tokensUpdated 7 mo ago
    Auto-check passed
  • Testing

    nth5693/gemini-kit

    Unified testing commands and patterns across frontend and backend.

    372 GitHub stars~259 tokensUpdated 7 mo ago
    Auto-check passed
  • Code Review

    nth5693/gemini-kit

    Systematic multi-perspective code review with consistent quality gates.

    372 GitHub stars~339 tokensUpdated 7 mo ago
    Auto-check passed
  • Session Resume

    nth5693/gemini-kit

    Resume context from previous session

    372 GitHub stars~411 tokensUpdated 7 mo ago
    Auto-check passed

Categories

Questions about Debug

What does Debug do?

Systematic debugging with structured reproduction and root cause analysis. Debug is an agent skill from nth5693/gemini-kit. Systematic debugging with structured reproduction and root cause analysis.

When should I use Debug?

Debug fits situations like: tasks that involve Debugging; tasks that involve Root cause analysis.

How do I install Debug in Claude Code?

Run `npx skills add nth5693/gemini-kit --skill debug -a claude-code`. Or copy the skill folder (skills/debug in nth5693/gemini-kit) into .claude/skills/debug in your project. Claude Code loads it when a task matches its description.

How do I install Debug in Codex?

Run `npx skills add nth5693/gemini-kit --skill debug -a codex`. Or copy the skill folder (skills/debug in nth5693/gemini-kit) into .agents/skills/debug in your project. Codex loads it when a task matches its description.

Can I use Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nth5693/gemini-kit --skill debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug, .gemini/skills/debug, .github/skills/debug and .opencode/skills/debug in your project.

What does Debug need to run?

SKILL.md names no scripts, command-line tools or credentials: Debug is instructions for the agent only.

Does Debug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Debug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Debug use?

Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debug use?

About 301 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Debug?

Skills that share tags, products or a category with Debug: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Graph-Based Bug Tracing (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug?

nth5693 (a GitHub user) maintains it in nth5693/gemini-kit, which has 372 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on March 7, 2026.

Source: nth5693/gemini-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.