debug

Stars12

Forks4

UpdatedApril 16, 2026 at 08:42

Investigate and fix bugs. Use when the user reports a bug, failing behavior, regression, flaky case, crash, panic, incorrect output, or asks to debug an issue.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

ai-pivot

ai-pivot/xbot

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	debug
description	Investigate and fix bugs. Use when the user reports a bug, failing behavior, regression, flaky case, crash, panic, incorrect output, or asks to debug an issue.

Debug

Goal

Turn vague bug reports into reproducible, verified fixes.

Default workflow

Define the failure clearly
- Restate the observed behavior, expected behavior, affected scope, and current evidence.
- Before changing code, define a verifiable success criterion for the fix.
Reproduce with a test first
- Prefer adding or updating an automated test that fails for the reported bug.
- Reuse the project's existing test style and location.
- If the bug is hard to express as a full test, create the smallest reproducible check possible (unit test, integration test, script, fixture, or command).
Fix only after reproduction exists
- Change code only after you can reproduce the issue with a failing test/check, unless reproduction is impossible in the current environment.
- Keep the fix scoped to the verified cause.
Verify the fix
- Re-run the reproduction test/check and confirm it now passes.
- Run the nearest related validation commands to catch regressions.
If user cooperation is required
- Use AskUser to ask focused questions with choices when possible — this reduces back-and-forth.
- Prepare everything the user needs before asking them to test:
  - exact command(s) to run
  - required environment variables / setup
  - expected output
  - log file path or log collection method
  - what result means success vs failure
- Ask concise questions only after the test plan is ready.
- When the user returns with logs/results, analyze both the logs and the user report before proposing the next step.

Rules

Prefer test-first debugging whenever the environment allows it.
Do not claim a bug is fixed without a passing reproduction check or an explicit explanation of why local verification is impossible.
If you cannot reproduce locally, say so clearly and switch to preparing the best user-runnable reproduction and logging plan.
When asking the user to help test, minimize their work; prepare commands, paths, and logging details for them. Use AskUser to ask targeted questions — provide choices when possible to reduce ambiguity.
Always report:
- how the bug was reproduced
- what changed
- how the fix was verified
- what remains uncertain

More from this repository

same repository

agent-creator

ai-pivot/xbot

Manage SubAgent roles: create, view, modify, delete, or install agent definitions. MUST activate when user asks to create/edit/view/inspect any agent, install agents from external sources, or when you need to look at agent files under ~/.xbot/agents/. Agents are universal — install whatever the user needs.

2026-07-0312

plugin-creator

ai-pivot/xbot

Create, modify, and manage xbot plugins. Use when the user asks to create a plugin, set up script plugins, configure widgets, register custom tools via plugins, or create channel plugins.

2026-07-0312

skill-creator

ai-pivot/xbot

Create, update, delete, or install skills. Use when the user asks to create a new skill, modify an existing skill, install/import a skill from external sources (GitHub, URLs), package scripts/assets into a skill, or discusses skill design and structure. Skills are universal agent capabilities — install whatever the user wants.

2026-07-0312

ai-config

ai-pivot/xbot

Guide for AI to configure xbot TUI, themes, subscriptions, and settings. Activate when the user asks to customize the TUI appearance, create themes, manage LLM subscriptions, or make bulk configuration changes.

2026-07-0112

plan

ai-pivot/xbot

Build implementation plans for complex tasks. Use when the user asks to plan, design an approach, or think through a task before coding. Also activate for large refactorings, multi-file changes, or when the user says 'plan first' or '/plan'.

2026-05-2012

post-dev

ai-pivot/xbot

Post-development cleanup: update AGENTS.md and docs/agent/ knowledge files to reflect code changes. MUST activate before git commit (or when user asks to commit/push). Also activate after any code modification that adds/removes files, changes architecture, or modifies core behavior.

2026-05-2012

Debug

Goal

Turn vague bug reports into reproducible, verified fixes.

Default workflow

Define the failure clearly

Restate the observed behavior, expected behavior, affected scope, and current evidence.
Before changing code, define a verifiable success criterion for the fix.

Reproduce with a test first

Prefer adding or updating an automated test that fails for the reported bug.
Reuse the project's existing test style and location.
If the bug is hard to express as a full test, create the smallest reproducible check possible (unit test, integration test, script, fixture, or command).

Fix only after reproduction exists

Change code only after you can reproduce the issue with a failing test/check, unless reproduction is impossible in the current environment.
Keep the fix scoped to the verified cause.

Verify the fix

Re-run the reproduction test/check and confirm it now passes.
Run the nearest related validation commands to catch regressions.

If user cooperation is required

Use AskUser to ask focused questions with choices when possible — this reduces back-and-forth.
Prepare everything the user needs before asking them to test:
- exact command(s) to run
- required environment variables / setup
- expected output
- log file path or log collection method
- what result means success vs failure
Ask concise questions only after the test plan is ready.
When the user returns with logs/results, analyze both the logs and the user report before proposing the next step.

Rules

Prefer test-first debugging whenever the environment allows it.

Do not claim a bug is fixed without a passing reproduction check or an explicit explanation of why local verification is impossible.

If you cannot reproduce locally, say so clearly and switch to preparing the best user-runnable reproduction and logging plan.

When asking the user to help test, minimize their work; prepare commands, paths, and logging details for them. Use AskUser to ask targeted questions — provide choices when possible to reduce ambiguity.

Always report:

how the bug was reproduced
what changed
how the fix was verified
what remains uncertain