skills.rest
sandeco
sandecoCOMMUNITY
Explore all skills by this author →
Website𝕏@sandecoGitHub

reversa-debugger

Registers bug reports as traceable canonical records linked to specs, code, and tests.

1.5k|405|Updated Apr 26, 2026
Search Tags:#traceability#deduplication#triage#bug tracking#legacy systems#SPEC-driven#issue registry
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-debugger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-debugger
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-debugger
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bug reports arrive as messy, unstructured complaints mixing multiple defects, screenshots, and guesses. This Skill turns each report into a canonical, traceable bug record organized by context, linked to the specification that defines expected behavior, the suspected code, and related bugs, without ever attempting to fix anything itself.

Core Features & Use Cases

  • Structured intake and triage: Captures user reports verbatim in intake/, collects evidence files, deduplicates against existing bugs, and classifies severity, priority, area, module, and feature using a controlled taxonomy.
  • SPEC-CODE-TEST-BUG traceability: Each bug gets a merge-safe canonical ID, links to the effective spec (original plus addenda), affected code, and typed relationships (caused-by, duplicate-of, regression-of) with epistemological states.
  • Express route and generated views: Small defects with an explicit fix request follow a minimal-registration express route that hands off to the fixer skill, while full flows generate context views (catalog, matrix, graph.html) under _reversa_bugs/<context>/generated/.
  • Use Case: A user says "the checkout is applying the discount twice." The Skill resolves the context, records the report, checks for duplicates, creates bugs/BUG-<date>-<suffix>/bug.md linked to the checkout spec section, and regenerates the context's traceability views.

Quick Start

Ask the agent to register a bug by describing the defect and its area, for example: "/reversa-debugger the credit system fails when approving limits above the configured threshold."

Frequently Asked Questions about reversa-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register a bug report with traceability to specs and code?▼

Invoke the skill with a description of the defect and its area. It resolves the context, records your report verbatim in an intake file, deduplicates against existing bugs, and creates a bug.md linked to the spec section, suspected code, and related bugs.

What is the difference between reversa-debugger and reversa-debugger-fix?▼

reversa-debugger only documents defects: intake, triage, classification, and traceability. It never modifies code. reversa-debugger-fix is the separate skill that performs the actual correction, and the express route hands off to it after minimal registration.

When should I use the express route instead of the full bug intake flow?▼

Use the express route when there is a single small, localized defect with an explicit fix request, no security suspicion, and no regression of a locked bug. Dense reports with multiple problems or serious defects should use the full triage flow.

Does this skill work with Claude Code, Cursor, and other AI agents?▼

Yes. The skill declares compatibility with Claude Code, Codex, Cursor, Gemini CLI, and other agents supporting the Agent Skills format. It reads project configuration from .reversa/state.json for language and output folder settings.

How are duplicate or recurring bugs handled?▼

The skill searches catalogs within and across contexts before creating a record and asks the user how to proceed when a probable duplicate exists. If the duplicate is locked with DONE.md, it registers a new bug with a regression-of relationship instead of modifying the locked one.

What happens when a reported defect has no matching specification?▼

The bug receives the spec-gap label and the record explicitly states the behavior was never specified. The question of whether it is a bug or an unspecified behavior stays open for the fix phase to resolve.

Related Skills

Explore More Software Engineering Skills→
Markson22Markson22

reversa-writer

Generate per-unit specification folders with requirements.md, design.md, and tasks.md from legacy systems.

Community
Advanced
SamyakJhaveriSamyakJhaveri

fix-bug

Automate a six-phase bug-fix workflow from reproduction to recording.

Community
Advanced
SullivanXiongSullivanXiong

knowledge-graph

Regenerate an interactive D3.js knowledge graph from Memory MCP data.

Community
Advanced
dmzoneilldmzoneill
2

create-jira-issue

Create Jira issues with code search context and Slack notifications.

Community
Advanced