// Review code for quality, bugs, security issues, and suggest improvements. Use when asked to review, audit, or improve code.
Generate a numbered Architecture Decision Record (ADR) following the standard nygard/MADR convention. Reads the target ADR directory to compute the next number and to surface candidates for cross-linking. Use when asked to document an architectural decision, draft an ADR, or capture a technical choice with its rationale.
Generate a polished CHANGELOG.md and release-notes.md from a local git repository (or a captured `.git-log.txt` dump). Groups commits by Conventional Commit type, writes both artifacts to the run output directory. Use when asked to draft release notes, summarize commits between tags, or produce a human-readable changelog.
Turn a CSV of operational data (sales, usage, signups, support tickets) into a multi-page styled PDF executive report with narrative + matplotlib charts. The LLM analyzes the data, picks what's interesting, writes the prose, and emits a structured render request that becomes a polished PDF. Use when given a CSV and asked for a report, summary, or analysis.
Analyze structured data (CSV/JSON), find patterns, generate insights, and suggest visualizations. Use for data analysis tasks.
Draft professional emails based on context, tone, and recipient. Use for composing business emails.
Turn a folder of Markdown notes (Obsidian vault, Notion export, plain repo docs) into a navigable static HTML knowledge base bundled as a single .zip file. Maintains a persistent concept graph across runs — concepts that appear in multiple runs gain prominence, and the index becomes denser over time. Use when given a Markdown vault and asked to publish, share, or render it as a browsable site.
| name | code-review |
| description | Review code for quality, bugs, security issues, and suggest improvements. Use when asked to review, audit, or improve code. |
You are an expert code reviewer. Analyze the provided code and produce a structured review.
Return a JSON object with:
review: A summary of the code quality (2-3 sentences)issues: An array of objects, each with severity (critical/warning/info), line (if applicable), and descriptionscore: A number 0-100 representing overall code qualityInput: A function with no error handling Output: Score ~60, issues include "No error handling for edge cases", "Missing input validation"