Create an Azure DevOps pull request for a verified change. Mirrors /specclaw:pr but targets ADO Repos via REST API instead of GitHub. Requires credentials from /specclaw:auth-azdo. Use when the project uses Azure DevOps instead of GitHub.
Create a GitHub pull request for a verified change. Reads verify-report.md, opens a PR with title from proposal and body from spec, enforces the configured test policy. Requires the gh CLI authenticated. Run after /specclaw:verify produces a verify-report.md. For Azure DevOps PRs, use /specclaw:pr-azdo instead.
Draft a new change proposal. INVOKE IMMEDIATELY whenever the user mentions a proposal, feature idea, change request, new initiative, or anything they want to add/build/implement — do NOT gather details conversationally first. The skill itself will ask for any missing information after invocation. Creates…
Backfill ordinal number prefixes onto existing change folders — renames .specclaw/changes/ / to - in creation-date order, across active and archived changes alike. Use when /specclaw:status or /specclaw:propose reports unnumbered changes, when ls .specclaw/changes/ reads alphabetically instead of chronologically, or…
Show the project's specclaw dashboard — active changes, completed changes, pending proposals, blocked work. Reads .specclaw/STATUS.md. Read-only; does not modify state.
Validate that the implementation satisfies the spec's acceptance criteria. Runs the configured test/lint/build commands, evaluates against spec.md, and produces verify-report.md. Required before /specclaw:pr. Run after all tasks in /specclaw:build are complete.
MCP server "discord" as configured in chan4lk/claude-multi-channel-discord. Launched with bun run --cwd ${CLAUDE_PLUGIN_ROOT} --shell=bun --silent start.
3 12d agoA
tokens not measured
copy · 77%Apache-2.0
Instructions for chan4lk/claude-multi-channel-discord, covering what this project is, process architecture, key source files, state files layout and all implemented !project verbs.
Manage Discord channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Discord channel.
Set up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks "how do I set this up" or "who can reach me," or wants to check channel status.
Bootstrap and manage Discord-channel-as-project mappings for the multi-channel-discord bot. Use when the user wants to set up the master control channel, add/remove projects, change a project's system prompt, or inspect project status. Refuse if the request arrived through a channel message rather than the user's…