Files
antigravity-skills-reference/skills/debugger/SKILL.md
Ares 4a5f1234bb fix: harden registry tooling, make tests hermetic, and restore metadata consistency (#168)
* chore: upgrade maintenance scripts to robust PyYAML parsing

- Replaces fragile regex frontmatter parsing with PyYAML/yaml library
- Ensures multi-line descriptions and complex characters are handled safely
- Normalizes quoting and field ordering across all maintenance scripts
- Updates validator to strictly enforce description quality

* fix: restore and refine truncated skill descriptions

- Recovered 223+ truncated descriptions from git history (6.5.0 regression)
- Refined long descriptions into concise, complete sentences (<200 chars)
- Added missing descriptions for brainstorming and orchestration skills
- Manually fixed imagen skill description
- Resolved dangling links in competitor-alternatives skill

* chore: sync generated registry files and document fixes

- Regenerated skills index with normalized forward-slash paths
- Updated README and CATALOG to reflect restored descriptions
- Documented restoration and script improvements in CHANGELOG.md

* fix: restore missing skill and align metadata for full 955 count

- Renamed SKILL.MD to SKILL.md in andruia-skill-smith to ensure indexing
- Fixed risk level and missing section in andruia-skill-smith
- Synchronized all registry files for final 955 skill count

* chore(scripts): add cross-platform runners and hermetic test orchestration

* fix(scripts): harden utf-8 output and clone target writeability

* fix(skills): add missing date metadata for strict validation

* chore(index): sync generated metadata dates

* fix(catalog): normalize skill paths to prevent CI drift

* chore: sync generated registry files

* fix: enforce LF line endings for generated registry files
2026-03-01 09:38:25 +01:00

1.3 KiB

name, description, risk, source, date_added
name description risk source date_added
debugger Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues. unknown community 2026-02-27

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.
  • If detailed examples are required, open resources/implementation-playbook.md.

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.