frostney

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.

Commits relevant changes, pushes a focused branch, and opens a templated draft pull request. Use when the user runs /create-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.

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.

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.

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.

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.

Cuts a release so the tag always contains its own changelog: computes the next version from the conventional commits, writes the changelog and bumps the version on a release branch, opens a release pull request, and only after it is squash-merged tags the merge commit and waits for CI to publish the GitHub release — never a changelog pull request that lands after the tag and isn't in the release. Uses a version passed in by the user, or otherwise recommends one from the changes since the last release and asks the user to confirm before proceeding. Defaults to git-cliff for changelog generation but works with any changelog tool or a hand-maintained changelog, and bumps the version with the project's own tooling regardless of language. Use when the user runs /create-release or asks to cut, tag, or publish a release, bump the version, or generate release notes.

Prepare LWPT for a release by running the full project and E2E gates, checking the latest cross-platform CI result, auditing architecture drift across source and documentation, previewing the changelog, applying approved truth-sync fixes, and opening a draft preparation PR. Stops before version selection, changelog generation, tagging, or publishing, which belong to /create-release. Use when the user runs /prepare-release or asks to prepare LWPT for a release.

Turns a raw idea or feature request (no GitHub issue) into a confirmed mini-spec by asking follow-up questions about scope, desired outcome, and success criteria, then implements it with the same rigor as /implement-issue: reads AGENTS.md/area context, VISION.md when present, and applicable stack/conventions skills, runs a full-context investigation, invokes the grill skill when registered, presents two to four distinct options, and stops for the user's choice before coding unless automatic mode was requested, updates the branch against origin's default branch, implements the chosen option, searches project context for DEFINITION_OF_READY.md before implementation, runs verification (UI/UX checks plus the project's full check gate), reviews against the spec's success criteria and project-context DEFINITION_OF_DONE.md before handoff, runs a /review code review, and always hands off via /create-pr. Use when the user runs /implement-idea or wants to build something that is not an existing issue.

Creates a well-structured GitHub issue from a tagline or short description in any repository, investigating for duplicates, reading VISION.md when present, and invoking the grill skill (grill-with-docs / grill-me) as a mandatory gate before drafting, using the project's issue template and label conventions, and capturing UI/UX context (screenshots, design references, accessibility, responsive, theme) when the change is user-facing. Use when the user runs /create-issue or asks to file a GitHub issue.

Validates a GitHub issue against the current codebase, reading the nearest AGENTS.md/CLAUDE.md, VISION.md when present, area context, and any applicable stack/conventions skills first. Runs a full-context investigation (real project commands, whole code path, no shortcuts), handles already-fixed issues by closing or adding regression tests, invokes the grill skill when registered, then presents implementation options and stops for the user's choice before coding unless automatic mode was requested. Updates the branch against origin's default branch, implements the chosen option, searches project context for DEFINITION_OF_READY.md before implementation, runs verification (UI/UX checks plus the project's full check gate), reviews against the issue's acceptance criteria and project-context DEFINITION_OF_DONE.md before handoff, runs a /review code review, and always hands off via /create-pr. Use when the user runs /implement-issue with an issue number.

Review a project's roadmap from freshly-pulled data — assess current state and release cadence, measure delivery velocity from history, and verify candidate work against the source — then produce a parallelized, throughput-anchored version plan, and (optionally, on confirmation) create the milestones and issues. Use when the user wants to review the roadmap, plan upcoming versions/releases, decide when to cut the next release, or sequence a backlog into a realistic plan.

Commits relevant local changes, merges the remote default branch when the branch is behind, pushes to the current PR branch, and refreshes PR title/body when stale. Use when the user runs /update-pr or asks to update a pull request with the latest commits.

Commits relevant local changes, pushes a focused branch, and opens a draft pull request on the current GitHub repository using the project's PR template (single or multi-template). Use when the user runs /create-pr.

An ambient lens that tilts technology choices toward the newest viable option so the work keeps up with the ever-changing times without leaving the known good route. It biases the default toward the latest stable release (including just-released majors), newly-stable language and platform features, modern tooling, and current AI models/capabilities, and allows pre-release channels (beta/RC/canary, and nightly only with a documented reason) when a concrete need justifies the climb. It sits beneath software-engineering-excellence: maintainability stays the tiebreaker, every adoption is verified live, pinned, reversible, free of known blockers, and green on the full validation gate, and decided choices and AGENTS.md Hard Constraints are never silently swapped. Use when selecting a dependency, framework, runtime, language feature, tool, or AI model; when picking or upgrading a version; or whenever deciding how current a technology choice should be.

Creates a well-structured GitHub issue from a tagline or short description in any repository, investigating for duplicates, reading VISION.md when present, and invoking the grill skill (grill-with-docs / grill-me) as a mandatory gate before drafting, using the project's issue template and label conventions, and capturing UI/UX context (screenshots, design references, accessibility, responsive, theme) when the change is user-facing. Use when the user runs /create-issue or asks to file a GitHub issue.

Runs a documentation-backed decision loop before implementation planning or issue drafting, using current source, docs, and ADR evidence to ask one sharp question at a time, record resolved terms in CONTEXT.md when present, and create ADRs only for hard-to-reverse decisions with real trade-offs. Use when the user invokes /grill-with-docs or when another workflow requires the grill gate before implementation planning or issue creation.

Turns a raw idea or feature request (no GitHub issue) into a confirmed mini-spec by asking follow-up questions about scope, desired outcome, and success criteria, then implements it with the same rigor as /implement-issue: reads AGENTS.md/area context, VISION.md when present, and applicable stack/conventions skills, runs a full-context investigation, invokes the grill skill when registered, presents exactly three options, and stops for the user's choice before coding unless automatic mode was requested, updates the branch against origin's default branch, implements the chosen option, searches project context for DEFINITION_OF_READY.md before implementation, runs verification (UI/UX checks plus the project's full check gate), reviews against the spec's success criteria and project-context DEFINITION_OF_DONE.md before handoff, runs a /review code review, and always hands off via /create-pr. Use when the user runs /implement-idea or wants to build something that is not an existing issue.

Validates a GitHub issue against the current codebase, reading the nearest AGENTS.md/CLAUDE.md, VISION.md when present, area context, and any applicable stack/conventions skills first. Runs a full-context investigation (real project commands, whole code path, no shortcuts), handles already-fixed issues by closing or adding regression tests, invokes the grill skill when registered, then presents implementation options and stops for the user's choice before coding unless automatic mode was requested. Updates the branch against origin's default branch, implements the chosen option, searches project context for DEFINITION_OF_READY.md before implementation, runs verification (UI/UX checks plus the project's full check gate), reviews against the issue's acceptance criteria and project-context DEFINITION_OF_DONE.md before handoff, runs a /review code review, and always hands off via /create-pr. Use when the user runs /implement-issue with an issue number.

Language-agnostic repo structure conventions used across the user's projects in any language — the user-facing README.md structure (name, logo, description, install, usage, optional background, contribution, references), the docs/ template (application, architecture, code-style, quick-start, tooling, deployment), the AGENTS.md template with a Hard Constraints section (symlinked to CLAUDE.md), nested area AGENTS.md for multi-area repos, optional CONTRIBUTING.md, the canonical VISION.md, DEFINITION_OF_READY.md, and DEFINITION_OF_DONE.md governance files, the pre-commit hook contract with Lefthook as the default and explicit alternatives, scripts directory in the project's own language, co-located tests, the .agents/skills folder symlinked to .claude/skills, and changelog generation with git-cliff. Stack-specific tools (test runners, linters, generators) live in the matching stack skill. Use when scaffolding or restructuring any repo, writing AGENTS.md or docs, or laying out folders.

Ambient engineering-quality skill that MUST be selected for any code edit, implementation, debugging pass, review fix, refactor, architecture change, test-harness change, or substantial technical investigation in any stack. Use this before acting on engineering work, especially after user correction or when scope, tooling, validation, or architecture might drift. Defines the standard for good and excellent engineering work, sitting above execution/workflow skills: grounding in reality, full-scope completeness, reuse over duplication, real validation, right-sized value, and maintainability as the governor. It prevents the agent from improvising its own definition of good, quietly narrowing scope, shipping only the happy path, duplicating code that already exists, swapping a decided approach, over-correcting after feedback, or claiming work is done without verifying it. Apply it even when no instruction asks for "quality" or "best practices" — it is the default standard for engineering work, not an add-on.

Creates a well-structured GitHub issue from a tagline or short description in any repository, investigating for duplicates and invoking the grill skill (grill-with-docs / grill-me) as a mandatory gate before drafting, using the project's issue template and label conventions, and capturing UI/UX context (screenshots, design references, accessibility, responsive, theme) when the change is user-facing. Use when the user runs /create-issue or asks to file a GitHub issue.

Turns a raw idea or feature request (no GitHub issue) into a confirmed mini-spec by asking follow-up questions about scope, desired outcome, and success criteria, then implements it with the same rigor as /implement-issue: reads AGENTS.md/area context and applicable stack/conventions skills, runs a full-context investigation, invokes the grill skill when registered, presents exactly three options and stops for the user's choice before coding, updates the branch against origin's default branch, implements the chosen option, searches project context for DEFINITION_OF_READY.md before implementation, runs verification (UI/UX checks plus the project's full check gate), reviews against the spec's success criteria and project-context DEFINITION_OF_DONE.md before handoff, runs a /review code review, and always hands off via /create-pr. Use when the user runs /implement-idea or wants to build something that is not an existing issue.

Validates a GitHub issue against the current codebase, reading the nearest AGENTS.md/CLAUDE.md, area context, and any applicable stack/conventions skills first. Runs a full-context investigation (real project commands, whole code path, no shortcuts), handles already-fixed issues by closing or adding regression tests, invokes the grill skill when registered, then presents implementation options and stops for the user's choice before coding. Updates the branch against origin's default branch, implements the chosen option, searches project context for DEFINITION_OF_READY.md before implementation, runs verification (UI/UX checks plus the project's full check gate), reviews against the issue's acceptance criteria and project-context DEFINITION_OF_DONE.md before handoff, runs a /review code review, and always hands off via /create-pr. Use when the user runs /implement-issue with an issue number.

Language-agnostic repo structure conventions used across the user's projects in any language — the user-facing README.md structure (name, logo, description, install, usage, optional background, contribution, references), the docs/ template (application, architecture, code-style, quick-start, tooling, deployment), the AGENTS.md template with a Hard Constraints section (symlinked to CLAUDE.md), nested area AGENTS.md for multi-area repos, optional CONTRIBUTING.md, the pre-commit hook contract with Lefthook as the default and explicit alternatives, scripts directory in the project's own language, co-located tests, the .agents/skills folder symlinked to .claude/skills, and changelog generation with git-cliff. Stack-specific tools (test runners, linters, generators) live in the matching stack skill. Use when scaffolding or restructuring any repo, writing AGENTS.md or docs, or laying out folders.

Commits relevant local changes, merges origin/main when the branch is behind, pushes to the current PR branch, and refreshes PR title/body when stale. Use when the user runs /update-pr or asks to update a pull request with the latest commits.

Reviews a completed workstream from conversation, repository, and forge evidence, uses grilling to agree durable lessons, and updates project vision and readiness/completion definitions after confirmation. Use when ending a substantial workstream or running a project retrospective.

Commits relevant changes, pushes a focused branch, and opens a templated draft pull request. Use when the user runs /create-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.

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.

Defines the user's default React-based stack across two project profiles — web (Next.js App Router) and universal (Expo Router) — sharing a common core (Bun-only, TypeScript, Tailwind on web / React Native StyleSheet on native, co-located bun test, single aggregator check, Vercel AI Gateway, Clerk auth, Convex data, Plop scaffolding, Lefthook pre-commit, AGENTS.md hard constraints), carrying the React-specific project structure (src/app routing both profiles, Atomic Design component folders, one-export-per-file naming where the filename matches the export), and pointing to convex-conventions and project-structure for deeper specifics. Use when scaffolding a new React-based app, upgrading deps, choosing tooling for an MVP, or deciding which profile a project belongs to.

Ambient engineering-quality standard sitting above the execution/workflow skills that defines what good and excellent work means: grounding in reality, full-scope completeness, reuse over duplication, real validation, right-sized value, and maintainability as the governor. It is the default, not an add-on, and MUST be selected for planning, orchestrating, developing, debugging, reviewing, refactoring, changing architecture or test harnesses, or substantial technical investigation, even when no instruction asks for "quality". It stops the agent improvising its own definition of good, narrowing scope, shipping only the happy path, patching a symptom over a structural problem, duplicating code, treating docs or comments as proof instead of leads, swapping a decided approach, over-correcting after feedback, or claiming work is done without verifying it. Use when beginning, planning, or coordinating technical work, and especially after a correction or when scope, tooling, validation, or architecture might drift.