Marco-Cricchio

ask-moh

Ask which skill or flow fits your situation, or how moh itself works. A router over the first-party workflow skills and the moh documentation (extensions, skills, core library, config).

Code & Development Listed

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

codebase-design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

gh-manager

Declarative, IaC-style GitHub repository management: keep repos, labels and branch protection in sync with a declared repos.yaml via init → plan → apply. Use when the user wants to make their repos match a declaration, standardize labels or branch protection across repositories, or audit drift between declared and live GitHub settings. Ported from gh-manager by David Lawson (@ddlaws0n), MIT.

moh-implementation-flow

Moh execution discipline for non-trivial implementation work. Load from implement before exploration.

prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

report-bug

File a bug or feature request against the moh repository on behalf of the user. Collects environment info and version, drafts the issue, and publishes it through the user's authenticated gh (with confirmation) — or hands over the web fallback when gh is missing.

session-memory

Maintain structured session notes for continuity across conversations. Use at the start of any project session, when asked to remember work, resume a session, or save progress.

tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

to-spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

triage

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.