known-good-route

Reviews a pull request, branch, or worktree against its claim, repository standards, and reproducible behavior, then optionally fixes selected findings or all in-scope findings. Use when the user runs /code-review or asks for an evidence-backed review of a bounded code change.

Audits the current repository for systemic correctness, architecture, simplification, clarity, test value, and operational risks using current source and reproducible probes. Use when the user runs /codebase-audit or asks for an evidence-backed review of a whole codebase or scoped subsystem.

Turns an unfiled idea into a confirmed mini-spec, implements and validates the selected approach, reviews it, and opens a draft pull request. Use when the user runs /implement-idea or asks to build something without an existing issue.

Validates and implements a GitHub issue against current repository evidence, runs the project's completion gate, reviews the change, and opens a draft pull request. Use when the user runs /implement-issue with an issue number.

Biases technology choices toward the newest viable option while preserving maintainability, live verification, reversibility, and decided constraints. Use when selecting or upgrading a dependency, runtime, tool, language feature, or AI model.

Applies the user's Convex backend conventions while deferring mechanics to upstream Convex skills and current APIs to the live Convex docs. Use when scaffolding, reviewing, or refactoring Convex functions, schemas, or auth.

Investigates and creates a project-aligned GitHub issue from a tagline or short description, using the repository's template, evidence, and labels. Use when the user runs /create-issue or asks to file a GitHub issue.

Commits relevant changes, pushes a focused branch, and opens a templated draft pull request. Use when the user runs /create-pr.

Prepares a changelog-first release and, only when explicitly requested, publishes it through the repository's single established release path. Use when the user asks to prepare, cut, tag, or publish a release, bump the version, or generate release notes.

Applies the user's git defaults: branch from the remote default, merge rather than rebase, never amend or force-push, and squash-merge pull requests. Use when branching, syncing, committing, pushing, or merging in the user's repos.

Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

Applies the user's language-agnostic repository layout, documentation, governance, hook, test, agent-file, and changelog conventions. Use when scaffolding or restructuring a repo, writing AGENTS.md or docs, or laying out folders.

Applies the user's Bun-based React stack across Next.js web and Expo universal profiles, deferring backend and repository details to their domain skills. Use when scaffolding a React app, upgrading dependencies, choosing MVP tooling, or selecting a project profile.

Resolves current pull-request review threads in place, validates and pushes fixes, and avoids new top-level comments. Use when the user runs /review-pr.

Reviews a roadmap from fresh project evidence and produces a verified, throughput-anchored version plan, with execution gated on confirmation. Use when reviewing a roadmap, planning releases, or sequencing a backlog.

Reviews a completed workstream from conversation, repository, and forge evidence, uses grilling to agree improvements to delivery speed, process, and codebase health, then applies selected documentation edits and follow-up ticket actions. Use when ending a substantial workstream or running a project retrospective.

Applies the user's ambient engineering bar: current evidence, complete in-scope solutions, reuse, real validation, right-sized value, and maintainability. Use for planning, implementing, debugging, reviewing, refactoring, architecture, or substantial technical investigation.

Commits relevant changes, merges the remote default when needed, pushes the current pull-request branch, and refreshes stale PR metadata. Use when the user runs /update-pr or asks to update a pull request.