MCP Prompts
Generated automatically at build time from the madtea repository - do not edit here. Source: docs/reference/prompts.md.
madtea registers its golden-path workflows as MCP prompts. A client that supports prompts (such as Claude Code) surfaces each one as a slash command — invoke it as /mcp__madtea__<name> followed by the prompt’s arguments.
| Prompt | Invocation | Title | Arguments |
|---|---|---|---|
file-issue | /mcp__madtea__file-issue | File a well-formed issue | title (required): concise issue title; body (optional): issue body: context, expected vs actual, repro steps (optional) |
finish-branch | /mcp__madtea__finish-branch | Finish the current branch | summary (required): what changed and why (PR body); closes (optional): comma-separated issue numbers to close on merge (optional; e.g. 42,57) |
reconcile | /mcp__madtea__reconcile | Reconcile a conflicted pull request | number (required): the pull request number to reconcile (e.g. 42) |
release | /mcp__madtea__release | Check release cadence and cut a release | — |
review | /mcp__madtea__review | Review a pull request | number (required): the pull request number to review (e.g. 42) |
standup | /mcp__madtea__standup | Recent activity summary | days (optional): how many days back to summarize (optional; default 7) |
start-feature | /mcp__madtea__start-feature | Start a feature branch | name (required): branch/feature name (e.g. fix-login or issue-42-rate-limit) |
triage | /mcp__madtea__triage | Triage the open backlog | target (optional): what to rank: omit for the current repo, or pass owner/repo, or a bare owner to aggregate a whole org |
Canonical source: docs/reference/prompts.md in the madtea repo.