autoreport-dev

Route autoreport repository work to the correct focused skill.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/tubtrb/autoreport --skill autoreport-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoreport-dev
Source: https://github.com/tubtrb/autoreport/tree/main/codex/skills/autoreport-dev
Command: npx skills add https://github.com/tubtrb/autoreport --skill autoreport-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes work in the local autoreport repository to the correct focused skill while keeping changes aligned with the current CLI, schema, PowerPoint, and web contracts.

Core Features & Use Cases

  • Provides a shared repo frame and governance surface for autoreport work.
  • Routes deeper work to one primary focused skill (e.g., autoreport-cli, report-schema, pptx-output, web-demo) to ensure alignment with current tests and contracts.
  • Reinforces preloads and surface mapping so contributors start from up-to-date guidance and avoid drift.

Quick Start

Identify the touched surface in autoreport (CLI, loaders, template writers, or web surfaces) and engage the most relevant focused skill to implement the change.

Frequently Asked Questions about autoreport-dev

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

FAQPage Schema
How do I route repository work to the correct development surface?

To route repository work, identify the touched surface—such as the CLI, loaders, template writers, or web demo—and engage the matching focused skill. This keeps changes aligned with current codebase contracts and tests.

What is the best way to manage autoreport schema and PowerPoint contract changes?

Managing schema and PowerPoint contracts involves routing tasks to focused skills like report-schema or pptx-output. This enforces repository-local guidance from AGENTS.md and README sources to prevent codebase drift.

How do I keep CLI and web demo updates aligned with existing tests?

Keeping CLI and web demo updates aligned requires referencing the relevant SKILL.md entries under codex/skills. This routing mechanism ensures contributors start from up-to-date preloads and surface mapping guidance.

Does autoreport-dev work without external dependencies?

Yes, autoreport-dev operates without external dependencies. It functions as a shared governance surface, directing repository work to primary focused skills based on internal CLI, schema, and web contracts.

When should I use a routing skill instead of a focused template writer skill?

Use a routing skill when you need to identify the primary surface for a broad change across CLI, schema, PowerPoint, or web contracts. Use focused skills directly only when the exact implementation target is already known.