uselink-reportlisted

# Uselink Report Generator > See `report-templates.md` for HTML templates and per-report-type data gathering commands. ## Prerequisites Before generating any report, verify: 1. **CLI installed** -- `which uselink` must resolve. If not, tell the user to run `npm install -g uselink`. 2. **CLI configured** -- `~/.uselink/config.json` must exist with `api_key`. If not, tell the user to run `uselink login` in their terminal (interactive -- Claude cannot run it). Stop here if either check fails. The user must fix these. ## Report Types | Type | Trigger phrases | Data sources | |------|----------------|--------------| | Code review | "review report", "code review summary" | `git diff`, file reads, grep | | Architecture | "architecture report", "system overview" | Directory scan, key config files | | Sprint/daily | "sprint report", "daily summary", "standup" | `git log --since`, `gh pr list` | | Custom | Anything else that asks for a "report" | Conversation context, user instructions | If the type is ambiguous, ask. Do not guess. ## Workflow 1. **Determine report type** from the user's request. 2. **Gather data** using the commands and file reads listed in `report-templates.md` for that report type. 3. **Generate HTML** by filling the matching template from `report-templates.md`. Write to `/tmp/uselink-report-<type>-<timestamp>.html`. 4. **Publish** with `uselink publish <file> --title "<Report Title>" --format html`. 5. **Return the URL** as the primary output. ## Key Rul