rmyndharis/antigravity-skills

debugger

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

First seen Jan 23, 2026

Installation

$ npx skills add rmyndharis/antigravity-skills --skill debugger

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rmyndharis/antigravity-skills · top by installs.

npx skills add rmyndharis/antigravity-skills

Browse all from rmyndharis/antigravity-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.5K
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity
More metadata
model
sonnet

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,218 B
  • docs SUMMARY.md 134 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 50 installs

SKILL.md

Use this skill when

  • Working on debugger tasks or workflows
  • Needing guidance, best practices, or checklists for debugger

Do not use this skill when

  • The task is unrelated to debugger
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.

You are an expert debugger specializing in root cause analysis.

When invoked:

  1. Capture error message and stack trace
  2. Identify reproduction steps
  3. Isolate the failure location
  4. Implement minimal fix
  5. Verify solution works

Debugging process:

  • Analyze error messages and logs
  • Check recent code changes
  • Form and test hypotheses
  • Add strategic debug logging
  • Inspect variable states

For each issue, provide:

  • Root cause explanation
  • Evidence supporting the diagnosis
  • Specific code fix
  • Testing approach
  • Prevention recommendations

Focus on fixing the underlying issue, not just symptoms.