AI Marketplaces Leaderboard

AskMatt

ChatGPT plugin

Choose the right Matt flow

View in ChatGPT directory
Featured
No

not on the featured shelf

Movement

From our daily snapshots over the last 30 days.

Rank by placement

#4999of 6,02249places down24h—7d
#4,888#5,075#5,262#5,449Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

Rank in Developer tools

#390of 53718places down24h—7d
#362#392#422#452#482Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

In its category

How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.

Developer tools390th of 537 by placement
#PluginPosition7d
387CompText Context#4992—
388CrowdStrike Falcon Foundry#4993—
389Debug#4997—
390AskMattThis page#4999—
391Revyl#5002—
392Go: Fintech#5009—
393GH Review Loop#5018—

All 537 Developer tools plugins

Use the original Ask Matt router when you do not remember which Matt Pocock engineering workflow fits. Bundles the complete Matt skill set so the chosen flow can run without another plugin.

Example prompts

  • “I have a feature idea and do not know which workflow fits”
  • “Something is broken and I am unsure which Matt skill to use”
  • “Help me choose the right workflow for this repository”

Skills

  • ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

  • claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

  • code-review

    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.

  • domain-modeling

    Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.

  • entry-ask-matt

    Use whenever the AskMatt plugin is selected. Route the request to the intended bundled workflow while keeping all dependencies internal to this plugin.

  • git-guardrails-claude-code

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

  • grill-me

    A relentless interview to sharpen a plan or design.

  • grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

  • grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

  • handoff

    Compact the current conversation into a handoff document for another agent to pick up.

Show all 39
  • implement

    Implement a piece of work based on a spec or set of tickets.

  • implement-spec

    Implement a specification in code.

  • improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

  • loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

  • migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

  • 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.

  • research

    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

  • resolving-merge-conflicts

    Use when you need to resolve an in-progress git merge/rebase conflict.

  • retro

    Conduct a retrospective on a coding session.

  • scaffold-exercises

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

  • setup-matt-pocock-skills

    Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

  • setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

  • setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.

  • 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.

  • teach

    Teach the user a new skill or concept, within this workspace.

  • to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

  • 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.

  • using-agent-skills

    Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.

  • wait-what

    Stop. That last message did not land: re-pitch it.

  • wayfinder

    Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

  • 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.

  • writing-beats

    Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

  • writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

  • writing-fragments

    Writing, explore: mine raw fragments, no structure yet.

  • writing-shape

    Writing, exploit: shape raw material into an article, paragraph by paragraph.

Categories
Made by
Saul Martí
Sign-in
On Install
Capabilities
Choose the right Matt flow
Availability
Available
Version
2.0.0
Keywords
engineering-suite, ask-matt, skills
Created
September 10, 2026