report

Detect, classify, and document errors in a structured format for automated resolution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of detecting, classifying, and reporting errors, ensuring they are sent to the correct repository for efficient resolution.

Core Features & Use Cases

  • Automated Error Reporting: Detects and reports build, runtime, test, dependency, or configuration errors.
  • Cross-Repository Reporting: Automatically identifies and reports errors to sibling repositories or allows manual specification of a target repository.
  • Wait-for-Resolution Mode: Monitors errors until they are resolved or a timeout is reached.
  • Use Case: When a build error occurs in your frontend repository, this Skill can automatically detect it, classify it as a 'build' error, and report it to the backend repository if it's a related issue, or to the frontend repository itself if it's a local problem.

Quick Start

Use the report skill to report the current error to the 'neotoma' repository.

Frequently Asked Questions about report

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

FAQPage Schema
How do I automate cross-repository error reporting for build and runtime failures?

Cross-repository error reporting automatically detects, classifies, and documents build, runtime, test, dependency, or configuration errors, routing them to the correct sibling repository for automated resolution.

What is wait-for-resolution mode for incident management automation?

Wait-for-resolution mode is an incident management feature that monitors reported errors until they are resolved or a configurable timeout is reached, polling at specified intervals to track status.

How do I report a build error from my frontend repository to a sibling backend repository?

To report a build error to a sibling repository, the system automatically detects and classifies it, then routes the structured error report to the specified target repository for resolution.

Can I manually specify a target repository when reporting runtime and dependency errors?

Yes, automated error reporting supports manual specification of a target repository, allowing you to override automatic sibling repository detection when classifying and documenting runtime or dependency errors.

How does automated error classification work for configuration and test failures?

Automated error classification works by detecting the error source and categorizing it as a build, runtime, test, dependency, or configuration failure before documenting it in a structured format for resolution.

What are the limitations of using automated error reporting for cross-repo incident management?

Limitations include dependency on configurable timeouts and poll intervals during wait-for-resolution mode, meaning monitoring will cease if the specified timeout is reached before the error is resolved.