code-reporting

Request a report on a specific topic such as the auth flow or chatbot architecture. The skill searches the codebase with grep and directory listing, reads the relevant files, traces the logic, and produces a structured Markdown report saved in a reports directory.

Each report contains a title and executive summary, an architectural overview with Mermaid diagrams, a deep-dive analysis of code patterns and security considerations, linked file references, and a recommendations section.

Every mentioned file must be a clickable Markdown link using the file:/// URI scheme with an absolute path. Specific sections can include line ranges, for example filename:L10-20 pointing to lines 10 through 20.

Reports are persisted as Markdown files in a reports directory created at the project root. Each file gets a descriptive name such as reports/auth-flow-analysis.md so it remains accessible in the codebase.

Report quality depends on the search keywords and files actually read during exploration. Large or poorly organized repositories may require narrower topic scoping, and diagrams reflect only the code paths that were traced.