johno/beads
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Add optional prefix parameter to /bd-init command

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Steve Yegge
2025-10-14 16:03:25 -07:00
parent a4d816d1f4
commit 747697c6c0
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.claude-plugin/commands/bd-init.md
View File

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