report-error

Collect error details and store structured reports in a sibling repository.

27|4|Updated Jun 19, 2025

Search Tags:#automation #debugging #troubleshooting #logging #error reporting #cross-repo

Ready to run

npx skills add https://github.com/markmhendrickson/neotoma --skill report-error

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: report-error
Source: https://github.com/markmhendrickson/neotoma/tree/main/.cursor/skills/report-error
Command: npx skills add https://github.com/markmhendrickson/neotoma --skill report-error

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reporting errors encountered by an agent, ensuring they are logged and tracked in the appropriate repository for systematic resolution.

Core Features & Use Cases

Automated Error Logging: Captures detailed error information, including stack traces and context.
Cross-Repository Reporting: Intelligently detects and reports errors to sibling repositories, or allows explicit targeting.
Wait-for-Resolution Mode: Optionally waits for the reported error to be resolved by a human or automated system.
Use Case: An agent working in a frontend repository encounters a build error originating from a shared backend library. This Skill can automatically detect that the error needs to be reported to the backend repository, log it there, and optionally wait for the backend team to fix it before the agent proceeds.

Quick Start

Use the report-error skill to report any encountered error to the most appropriate repository.

Frequently Asked Questions about report-error

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

FAQPage Schema

How do I automate error reporting across multiple repositories?▼

To automate cross-repo error reporting, this Skill collects error details, classifies them, and stores structured reports directly in a target sibling repository's `.cursor/error_reports/` directory.

How does cross-repository error detection work when an agent encounters a build failure?▼

Cross-repository error detection works by automatically identifying the appropriate target repository based on the error's origin, analyzing context such as MCP calls and file paths to determine where the structured report should be logged.

Can I pause agent execution and wait for a reported error to be resolved?▼

Yes, you can pause agent execution using the optional wait-for-resolution functionality, which allows you to configure specific timeouts and polling intervals to wait for the reported error to be fixed before proceeding.

What is the best way to log stack traces and context from agent operations into a sibling repository?▼

The best way to log stack traces and context into a sibling repository is to use automated error logging that captures detailed error information and systematically stores it as structured reports in the target directory.

Does this error reporting approach work without explicit repository targeting?▼

Yes, it works without explicit targeting by supporting auto-detection of the target repository, intelligently routing error reports to the correct sibling repository based on the origin of the error.