What problem does it solve? Teams need a consistent, machine-readable way to record repository health findings such as security audits, performance checks, and uptime scans, but ad-hoc notes lack structure and are hard to filter or track over time. ## Core Features & Use Cases - Structured Report Format: Produces Markdown files with YAML frontmatter defining title, category, status, summary, timestamp, and optional metrics, tables, and markdown sections. - Directory-Based Tagging: Places reports in a reports/ directory where subdirectories automatically become tags for filtering and organization. - Git Workflow Integration: Commits reports to a dedicated reports git branch, including instructions for creating the orphan branch on first use. - Use Case: After running a dependency vulnerability scan, ask the agent to generate a security report; it writes reports/security/dependency-scan.md with severity metrics, a table of affected packages, and a failing status, then commits it to the reports branch. ## Quick Start Ask the agent to generate a security audit report for this repository and commit it to the reports branch.
