What problem does it solve?
When an agent encounters a bug in a skill, capability, or preset, it needs a consistent, evidence-backed way to document the problem and route it to the right people before any GitHub issue is filed. This reference provides the canonical report skeleton and delivery rules so reports are complete, durable, and correctly routed.
Core Features & Use Cases
- Structured Report Skeleton: Defines a fixed subject line format and body sections — what's wrong, where, reproduction steps, expected vs actual behavior, severity (blocking/major/minor/cosmetic), and an optional suggested fix — that double as a GitHub-flavored Markdown issue body.
- Channel-Aware Delivery: Instructs agents to send the report via LingTai internal email to the parent avatar and the human, or through the human's active chat channel such as Telegram, before any filing decision.
- Repository Routing Guidance: Directs reports to the Lingtai-AI/lingtai umbrella issue tracker, with fallback guidance for kernel-specific issues and self-healing notes when the template itself is stale.
- Use Case: An agent discovers a documented feature is broken, gathers reproduction evidence, fills in the template, and mails the structured report to its parent and the human for consent before filing on GitHub.
Quick Start
Load the issue report template and assemble a structured bug report with reproduction steps and severity, then send it to my parent avatar and me by email.
