debug

Triage and debug reported codebase errors with a background watcher process.

27|4|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/markmhendrickson/neotoma --skill debug-markmhendrickson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/markmhendrickson/neotoma/tree/main/.cursor/skills/debug
Command: npx skills add https://github.com/markmhendrickson/neotoma --skill debug-markmhendrickson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of identifying, debugging, and resolving errors reported within your codebase, ensuring smoother development cycles and faster issue resolution.

Core Features & Use Cases

  • Error Triage: Automatically identifies and prioritizes pending errors based on severity and timestamp.
  • Automated Debugging: Integrates with bug-fixing tools to attempt automatic resolution of common issues.
  • Watcher Management: Manages a background process to continuously monitor for new errors.
  • Use Case: When a critical build error occurs, this Skill can automatically detect it, attempt a fix using predefined rules, and update the error status, freeing up developers to focus on more complex tasks.

Quick Start

Run /debug to check for and debug pending errors in the current repository.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I automatically debug and resolve build errors in my codebase?

Automated debugging resolves build errors by triaging pending issues, integrating with bug-fixing commands to attempt fixes, and updating error status. Run the debug command to check and resolve pending errors in the current repository.

Can I monitor for new errors continuously in the background?

Yes, continuous error monitoring is supported through a background watcher process. The watcher runs persistently to detect new errors automatically, requiring process control and file system operations for report management.

How does automated error triage prioritize issues for resolution?

Error triage prioritizes pending errors based on severity and timestamp. This automated mechanism identifies and ranks issues, ensuring critical build errors are addressed first before attempting automated resolution.

Does this automated debugging workflow support cross-repository error checking?

Yes, cross-repository error checking is supported. This allows the debugging workflow to identify and resolve reported errors across multiple repositories, extending automated resolution beyond a single codebase.

What is the best way to handle error reports and file system operations during automated debugging?

Automated debugging handles error reports through file system operations for report management. Robust error handling ensures report files are created, updated, and managed correctly during the triage and resolution process.

When should I not use automated debugging for codebase errors?

Automated debugging should not be relied upon for complex issues beyond common error patterns. It attempts resolution using predefined rules, meaning developers must manually resolve errors that fall outside standard automated fixing capabilities.