bug-doc-required

What problem does it solve?

This skill ensures bug reports and analysis documents follow a strict, discoverable structure so investigations are reproducible, affected modules are accurately identified, and root causes are traced without ad-hoc code rescanning.

Core Features & Use Cases

• Mandatory template enforcement: enforces the fixed chapter order, naming conventions, and directory-per-bug rule under docs/bug/.
• Context preloading and indexing: instructs loading project overview and related module docs, and requires doc-index-required to read and update INDEX.md.
• Precise code mapping and diagrams: requires full class names, file paths with verified line numbers, and three Mermaid diagrams (sequence, flow, swimlane) to represent interactions, decisions, and cross-layer calls.
• Use Case: When a developer reports an NPE, timeout, or functional failure, run this skill to produce a compliance-ready bug analysis that includes reproduction steps, logs, involved classes, key code paths, root cause table, and prioritized fixes.

Quick Start

Invoke the bug-doc-required skill to create a standards-compliant bug analysis for "[brief bug summary]" including reproduction steps, logs, full class names, key code paths, and sequence/flow/swimlane diagrams.