Fetch public URLs/articles/docs/blogs and save clean Markdown with source URL, headings, lists, links, and code blocks. Use when the source is a URL. Not for converting local files (use markitdown) or condensing/summarizing content (use the /summarize-article…
Initialize state-of-the-art greenfield Python projects with current stable Python, uv, uv_build, Ruff, ty, pytest, a src layout, locked dependencies, and CI. Use when creating a new Python library, packaged application, CLI, service, worker, or standalone…
Sharp professional roast-style critique for code, architecture, docs, UI, specs, plans, prompts, or ideas when user asks for brutal feedback. Not for actionable line-level code review (use code-review-excellence) or interactive plan interrogation (use…
Use when converting local PDFs, Office files, images, or documents to Markdown or structured text. Defaults to Docling; uses MarkItDown only for its distinct fallback formats.
Implement a bounded code change from a request, spec, or implementation plan. Use when executing implementation work and choosing between quick, bounded, and tracked modes. Not for producing a spec (use to-spec) or an implementation plan (use to-plan) before…
Collapses deterministic multi-step repository research, aggregation, indexing, validation, and transformation into one small purpose-built local script and one Bash run. Use when a task would otherwise require 6+ related read/search/tool calls, iterates over…
Process open .ai-review.json code-review comments in the current Git repository when the user explicitly asks to work through, resolve, or inspect those comments.
Review a concrete change against an explicit focus: plan/spec fidelity, correctness, security, performance, tests, maintainability, architecture, or full review. Use for PRs, branches, implementation output, and targeted risk reviews. Not for grilling a…