bruno-apilisted

# Bruno API Documentation Generator Skill ## Inputs & Modes This Skill expects one of: - A path to a single Bruno file (usually `*.bru`), OR - `--scan <dir>` to analyze all `.bru` files under a directory. Optional flags: - `--dry-run` – produce an analysis plan only (no deep codebase search). - `--output <path>` – write the generated markdown documentation to a file. If inputs are missing or ambiguous, ask the user to confirm: - Which `.bru` file(s) to analyze. - Whether they want `--dry-run` or full documentation. - Whether an output file should be written. ## Output Shape & Severity Tags ### Dry-run output Return a short plan containing: - Endpoint summary: method, URL, auth, and any detected params/body. - Where you will look in the Django codebase (specific file paths/directories). - Which documentation sections will be generated. - Complexity notes (e.g., “DRF ViewSet + serializer” vs “Ninja router + schema”). ### Full documentation output Generate a single markdown document for each endpoint using this structure: - `# <Endpoint Name>` - ``<METHOD> <URL Pattern>`` - **Authentication**, **Permissions**, **Multi-tenant** - `## Overview` - `## Request` (headers + params/body with types/validation) - `## Response` (success example + common error cases) - `## Implementation Details` (URL config + view + serializer/schema; always with `file.py:line`) - `## Business Logic` (step-by-step, include side effects like tasks/external calls) - `## Frontend Integration` (