Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/keycloak-mcp:issue descriptionThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# MCP Issue Report an issue with a Keycloak MCP tool. Invoke the `mcp-issue` skill to guide the user through documenting the problem. The server is **Keycloak** — pass this context to the skill so it skips server identification. Arguments: `$ARGUMENTS` If arguments were provided, treat them as the initial problem description and pass to the skill (skip the "what happened?" question in Step 1).
Report an issue with a Keycloak MCP tool. Invoke the mcp-issue skill to guide the user through documenting the problem. The server is Keycloak — pass this context to the skill so it skips server identification.
Arguments: $ARGUMENTS
If arguments were provided, treat them as the initial problem description and pass to the skill (skip the "what happened?" question in Step 1).
npx claudepluginhub unctad-eregistrations/plugin-marketplace --plugin keycloak-mcp/issueCreates a structured GitHub issue with type classification, title prefix, and repository routing, designed for downstream pipeline consumption.
/issueRefines Linear issues or user requests into structured PRDs or Bug Briefs via clarifying questions, then syncs the Markdown output back to Linear.
/issueResolves GitHub issues systematically: triages, investigates root causes with git/gh cli, implements tested fixes, and creates PRs. Requires issue ID or URL.
/issueCreates TASK, BUG, or SPIKE work items from natural language description using AI type detection, user confirmation, optional spec linkage, and numeric ID directory with skeleton file.