From 747697c6c0b7bc1a1a0ce160d971a10dcf9178fb Mon Sep 17 00:00:00 2001 From: Steve Yegge Date: Tue, 14 Oct 2025 16:03:25 -0700 Subject: [PATCH] feat: Add optional prefix parameter to /bd-init command MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Allow users to specify a custom issue prefix when initializing beads: /bd-init myproject If no prefix is provided, defaults to current directory name (existing behavior). Changes: - Add argument-hint: [prefix] to command frontmatter - Update command description to document $1 parameter usage - Pass prefix to MCP init tool when provided The MCP init tool already supported the prefix parameter, this just exposes it through the slash command interface. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .claude-plugin/commands/bd-init.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/.claude-plugin/commands/bd-init.md b/.claude-plugin/commands/bd-init.md index 9fceb08e..46f665ba 100644 --- a/.claude-plugin/commands/bd-init.md +++ b/.claude-plugin/commands/bd-init.md @@ -1,14 +1,18 @@ --- description: Initialize beads in the current project +argument-hint: [prefix] --- Initialize beads issue tracking in the current directory. -Use the beads MCP `init` tool to set up a new beads database. +If a prefix is provided as $1, use it as the issue prefix (e.g., "myproject" creates issues like myproject-1, myproject-2). If not provided, the default is the current directory name. + +Use the beads MCP `init` tool with the prefix parameter (if provided) to set up a new beads database. After initialization: 1. Show the database location -2. Explain the basic workflow (or suggest running `/bd-workflow`) -3. Suggest creating the first issue with `/bd-create` +2. Show the issue prefix that will be used +3. Explain the basic workflow (or suggest running `/bd-workflow`) +4. Suggest creating the first issue with `/bd-create` If beads is already initialized, inform the user and show project stats using the `stats` tool.