fix(docgen): generate CLI docs in one process (#4474)
Add a bulk help docs writer that emits the root CLI reference and website command pages from a single Cobra walk. Update the shell generator to call that mode, preserve the pure-Go docs binary guard, and refresh historical versioned CLI docs only when release snapshotting requests a specific version. Agent-Signature: codex-gpt-5.5-medium on behalf of matt wilkie
This commit is contained in:
parent
427fdd0c85
commit
dfa8ea4813
64 changed files with 356 additions and 244 deletions
|
|
@ -21,7 +21,7 @@ For routine maintenance, prefer 'bd doctor --fix' which handles common repairs
|
|||
automatically. Use these admin commands for targeted database operations.
|
||||
|
||||
```
|
||||
bd admin
|
||||
bd admin [flags]
|
||||
```
|
||||
|
||||
### bd admin cleanup
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Configuration can be set via 'bd config' or environment variables:
|
|||
ado.url / AZURE_DEVOPS_URL - Custom base URL (on-prem)
|
||||
|
||||
```
|
||||
bd ado
|
||||
bd ado [flags]
|
||||
```
|
||||
|
||||
### bd ado projects
|
||||
|
|
@ -28,7 +28,7 @@ bd ado
|
|||
List Azure DevOps projects that the configured token has access to.
|
||||
|
||||
```
|
||||
bd ado projects
|
||||
bd ado projects [flags]
|
||||
```
|
||||
|
||||
### bd ado pull
|
||||
|
|
@ -70,7 +70,7 @@ bd ado push [bead-ids...] [flags]
|
|||
Display current Azure DevOps configuration and sync status.
|
||||
|
||||
```
|
||||
bd ado status
|
||||
bd ado status [flags]
|
||||
```
|
||||
|
||||
### bd ado sync
|
||||
|
|
|
|||
|
|
@ -19,5 +19,5 @@ Examples:
|
|||
bd assign bd-123 "" # unassign
|
||||
|
||||
```
|
||||
bd assign <id> <name>
|
||||
bd assign <id> <name> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Each line is one event. This file is intended to be versioned in git and used fo
|
|||
Entries are append-only. Labeling creates a new "label" entry that references a parent entry.
|
||||
|
||||
```
|
||||
bd audit
|
||||
bd audit [flags]
|
||||
```
|
||||
|
||||
### bd audit label
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ DoltHub is recommended for cloud backup:
|
|||
Set DOLT_REMOTE_USER and DOLT_REMOTE_PASSWORD for authentication.
|
||||
|
||||
```
|
||||
bd backup
|
||||
bd backup [flags]
|
||||
```
|
||||
|
||||
### bd backup init
|
||||
|
|
@ -50,7 +50,7 @@ DoltHub (recommended for cloud backup):
|
|||
After adding, run 'bd backup sync' to push your data.
|
||||
|
||||
```
|
||||
bd backup init <path>
|
||||
bd backup init <path> [flags]
|
||||
```
|
||||
|
||||
**Aliases:** add
|
||||
|
|
@ -63,7 +63,7 @@ This unregisters the backup remote from Dolt and removes the local
|
|||
backup configuration. The backup data at the destination is not deleted.
|
||||
|
||||
```
|
||||
bd backup remove
|
||||
bd backup remove [flags]
|
||||
```
|
||||
|
||||
**Aliases:** rm
|
||||
|
|
@ -99,7 +99,7 @@ bd backup restore [path] [flags]
|
|||
Show last backup status
|
||||
|
||||
```
|
||||
bd backup status
|
||||
bd backup status [flags]
|
||||
```
|
||||
|
||||
### bd backup sync
|
||||
|
|
@ -114,5 +114,5 @@ The backup is atomic — if the sync fails, the previous backup state is preserv
|
|||
Run 'bd backup init <path>' first to configure a destination.
|
||||
|
||||
```
|
||||
bd backup sync
|
||||
bd backup sync [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -20,5 +20,5 @@ Examples:
|
|||
bd branch feature-xyz # Create a new branch named feature-xyz
|
||||
|
||||
```
|
||||
bd branch [name]
|
||||
bd branch [name] [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -62,5 +62,5 @@ bd comments add [issue-id] [text] [flags]
|
|||
Invalid — use bd comments <issue-id> to list comments
|
||||
|
||||
```
|
||||
bd comments list
|
||||
bd comments list [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ See each sub-command's help for details on how to use the generated script.
|
|||
|
||||
|
||||
```
|
||||
bd completion
|
||||
bd completion [flags]
|
||||
```
|
||||
|
||||
### bd completion bash
|
||||
|
|
|
|||
|
|
@ -79,7 +79,7 @@ Examples:
|
|||
bd config unset jira.url
|
||||
|
||||
```
|
||||
bd config
|
||||
bd config [flags]
|
||||
```
|
||||
|
||||
### bd config apply
|
||||
|
|
@ -131,7 +131,7 @@ Examples:
|
|||
bd config drift --json
|
||||
|
||||
```
|
||||
bd config drift
|
||||
bd config drift [flags]
|
||||
```
|
||||
|
||||
### bd config get
|
||||
|
|
@ -139,7 +139,7 @@ bd config drift
|
|||
Get a configuration value
|
||||
|
||||
```
|
||||
bd config get <key>
|
||||
bd config get <key> [flags]
|
||||
```
|
||||
|
||||
### bd config list
|
||||
|
|
@ -147,7 +147,7 @@ bd config get <key>
|
|||
List all configuration
|
||||
|
||||
```
|
||||
bd config list
|
||||
bd config list [flags]
|
||||
```
|
||||
|
||||
### bd config set
|
||||
|
|
@ -221,7 +221,7 @@ bd config show [flags]
|
|||
Delete a configuration value
|
||||
|
||||
```
|
||||
bd config unset <key>
|
||||
bd config unset <key> [flags]
|
||||
```
|
||||
|
||||
### bd config validate
|
||||
|
|
@ -239,5 +239,5 @@ Checks:
|
|||
bd config validate --json
|
||||
|
||||
```
|
||||
bd config validate
|
||||
bd config validate [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -22,5 +22,5 @@ Examples:
|
|||
|
||||
|
||||
```
|
||||
bd context
|
||||
bd context [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ bd dep add [issue-id] [depends-on-id] [flags]
|
|||
Detect dependency cycles
|
||||
|
||||
```
|
||||
bd dep cycles
|
||||
bd dep cycles [flags]
|
||||
```
|
||||
|
||||
### bd dep list
|
||||
|
|
@ -129,7 +129,7 @@ Examples:
|
|||
bd relate bd-123 bd-456 # Create see-also connection
|
||||
|
||||
```
|
||||
bd dep relate <id1> <id2>
|
||||
bd dep relate <id1> <id2> [flags]
|
||||
```
|
||||
|
||||
### bd dep remove
|
||||
|
|
@ -137,7 +137,7 @@ bd dep relate <id1> <id2>
|
|||
Remove a dependency
|
||||
|
||||
```
|
||||
bd dep remove [issue-id] [depends-on-id]
|
||||
bd dep remove [issue-id] [depends-on-id] [flags]
|
||||
```
|
||||
|
||||
**Aliases:** rm
|
||||
|
|
@ -182,5 +182,5 @@ Example:
|
|||
bd unrelate bd-abc bd-xyz
|
||||
|
||||
```
|
||||
bd dep unrelate <id1> <id2>
|
||||
bd dep unrelate <id1> <id2> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -23,5 +23,5 @@ Examples:
|
|||
bd diff abc123 def456 # Compare two specific commits
|
||||
|
||||
```
|
||||
bd diff <from-ref> <to-ref>
|
||||
bd diff <from-ref> <to-ref> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ Examples:
|
|||
bd dolt test
|
||||
|
||||
```
|
||||
bd dolt
|
||||
bd dolt [flags]
|
||||
```
|
||||
|
||||
### bd dolt clean-databases
|
||||
|
|
@ -113,7 +113,7 @@ project's Dolt data directory are eligible for cleanup. Other projects'
|
|||
servers are preserved.
|
||||
|
||||
```
|
||||
bd dolt killall
|
||||
bd dolt killall [flags]
|
||||
```
|
||||
|
||||
### bd dolt pull
|
||||
|
|
@ -172,7 +172,7 @@ Subcommands:
|
|||
remove <name> Remove a remote
|
||||
|
||||
```
|
||||
bd dolt remote
|
||||
bd dolt remote [flags]
|
||||
```
|
||||
|
||||
#### bd dolt remote add
|
||||
|
|
@ -180,7 +180,7 @@ bd dolt remote
|
|||
Add a Dolt remote
|
||||
|
||||
```
|
||||
bd dolt remote add <name> <url>
|
||||
bd dolt remote add <name> <url> [flags]
|
||||
```
|
||||
|
||||
#### bd dolt remote list
|
||||
|
|
@ -188,7 +188,7 @@ bd dolt remote add <name> <url>
|
|||
List configured Dolt remotes
|
||||
|
||||
```
|
||||
bd dolt remote list
|
||||
bd dolt remote list [flags]
|
||||
```
|
||||
|
||||
#### bd dolt remote remove
|
||||
|
|
@ -196,7 +196,7 @@ bd dolt remote list
|
|||
Remove a Dolt remote
|
||||
|
||||
```
|
||||
bd dolt remote remove <name>
|
||||
bd dolt remote remove <name> [flags]
|
||||
```
|
||||
|
||||
### bd dolt set
|
||||
|
|
@ -233,7 +233,7 @@ bd dolt set <key> <value> [flags]
|
|||
Show current Dolt configuration with connection status
|
||||
|
||||
```
|
||||
bd dolt show
|
||||
bd dolt show [flags]
|
||||
```
|
||||
|
||||
### bd dolt start
|
||||
|
|
@ -247,7 +247,7 @@ The server auto-starts transparently when needed, so manual start is rarely
|
|||
required. Use this command for explicit control or diagnostics.
|
||||
|
||||
```
|
||||
bd dolt start
|
||||
bd dolt start [flags]
|
||||
```
|
||||
|
||||
### bd dolt status
|
||||
|
|
@ -263,7 +263,7 @@ sql-server) — pings the configured endpoint via SQL and reports
|
|||
reachability, server version, and database.
|
||||
|
||||
```
|
||||
bd dolt status
|
||||
bd dolt status [flags]
|
||||
```
|
||||
|
||||
### bd dolt stop
|
||||
|
|
@ -294,5 +294,5 @@ This verifies that:
|
|||
Use this before switching to server mode to ensure the server is running.
|
||||
|
||||
```
|
||||
bd dolt test
|
||||
bd dolt test [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Generated from `bd help --doc epic`
|
|||
Epic management commands
|
||||
|
||||
```
|
||||
bd epic
|
||||
bd epic [flags]
|
||||
```
|
||||
|
||||
### bd epic close-eligible
|
||||
|
|
|
|||
|
|
@ -20,5 +20,5 @@ Federation enables synchronized issue tracking across multiple workspaces,
|
|||
each maintaining their own Dolt database while sharing updates via remotes.
|
||||
|
||||
```
|
||||
bd federation
|
||||
bd federation [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -19,5 +19,5 @@ Examples:
|
|||
bd forget auth-jwt
|
||||
|
||||
```
|
||||
bd forget <key>
|
||||
bd forget <key> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Commands:
|
|||
show Show formula details, steps, and composition rules
|
||||
|
||||
```
|
||||
bd formula
|
||||
bd formula [flags]
|
||||
```
|
||||
|
||||
### bd formula convert
|
||||
|
|
@ -105,5 +105,5 @@ Examples:
|
|||
bd formula show security-audit --json
|
||||
|
||||
```
|
||||
bd formula show <formula-name>
|
||||
bd formula show <formula-name> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Examples:
|
|||
bd gate resolve <id> # Close a gate manually
|
||||
|
||||
```
|
||||
bd gate
|
||||
bd gate [flags]
|
||||
```
|
||||
|
||||
### bd gate add-waiter
|
||||
|
|
@ -45,7 +45,7 @@ The waiter is typically the worker's address (e.g., "my-project/workers/agent-1"
|
|||
This is used by 'bd done --phase-complete' to register for gate wake notifications.
|
||||
|
||||
```
|
||||
bd gate add-waiter <gate-id> <waiter>
|
||||
bd gate add-waiter <gate-id> <waiter> [flags]
|
||||
```
|
||||
|
||||
### bd gate check
|
||||
|
|
@ -203,5 +203,5 @@ Display details of a gate issue including its waiters.
|
|||
This is similar to 'bd show' but validates that the issue is a gate.
|
||||
|
||||
```
|
||||
bd gate show <gate-id>
|
||||
bd gate show <gate-id> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Configuration can be set via 'bd config' or environment variables:
|
|||
github.url / GITHUB_API_URL - Custom API URL (GitHub Enterprise)
|
||||
|
||||
```
|
||||
bd github
|
||||
bd github [flags]
|
||||
```
|
||||
|
||||
### bd github pull
|
||||
|
|
@ -62,7 +62,7 @@ bd github push [bead-ids...] [flags]
|
|||
List GitHub repositories that the configured token has access to.
|
||||
|
||||
```
|
||||
bd github repos
|
||||
bd github repos [flags]
|
||||
```
|
||||
|
||||
### bd github status
|
||||
|
|
@ -70,7 +70,7 @@ bd github repos
|
|||
Display current GitHub configuration and sync status.
|
||||
|
||||
```
|
||||
bd github status
|
||||
bd github status [flags]
|
||||
```
|
||||
|
||||
### bd github sync
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Configuration can be set via 'bd config' or environment variables:
|
|||
gitlab.default_project_id / GITLAB_DEFAULT_PROJECT_ID - Project for creating issues in group mode
|
||||
|
||||
```
|
||||
bd gitlab
|
||||
bd gitlab [flags]
|
||||
```
|
||||
|
||||
### bd gitlab projects
|
||||
|
|
@ -28,7 +28,7 @@ bd gitlab
|
|||
List GitLab projects that the configured token has access to.
|
||||
|
||||
```
|
||||
bd gitlab projects
|
||||
bd gitlab projects [flags]
|
||||
```
|
||||
|
||||
### bd gitlab pull
|
||||
|
|
@ -70,7 +70,7 @@ bd gitlab push [bead-ids...] [flags]
|
|||
Display current GitLab configuration and sync status.
|
||||
|
||||
```
|
||||
bd gitlab status
|
||||
bd gitlab status [flags]
|
||||
```
|
||||
|
||||
### bd gitlab sync
|
||||
|
|
|
|||
|
|
@ -60,5 +60,5 @@ Check the dependency graph for cycles, orphans, and other integrity issues.
|
|||
Returns exit code 0 if the graph is clean, 1 if issues are found.
|
||||
|
||||
```
|
||||
bd graph check
|
||||
bd graph check [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ The hooks provide:
|
|||
- prepare-commit-msg: Add agent identity trailers for forensics
|
||||
|
||||
```
|
||||
bd hooks
|
||||
bd hooks [flags]
|
||||
```
|
||||
|
||||
### bd hooks install
|
||||
|
|
@ -60,7 +60,7 @@ bd hooks install [flags]
|
|||
Show the status of bd git hooks (installed, outdated, missing).
|
||||
|
||||
```
|
||||
bd hooks list
|
||||
bd hooks list [flags]
|
||||
```
|
||||
|
||||
### bd hooks run
|
||||
|
|
@ -79,7 +79,7 @@ The thin shim pattern ensures hook logic is always in sync with the
|
|||
installed bd version - upgrading bd automatically updates hook behavior.
|
||||
|
||||
```
|
||||
bd hooks run <hook-name> [args...]
|
||||
bd hooks run <hook-name> [args...] [flags]
|
||||
```
|
||||
|
||||
### bd hooks uninstall
|
||||
|
|
@ -87,5 +87,5 @@ bd hooks run <hook-name> [args...]
|
|||
Remove bd git hooks from .git/hooks/ directory.
|
||||
|
||||
```
|
||||
bd hooks uninstall
|
||||
bd hooks uninstall [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ SUBCOMMANDS:
|
|||
human stats Show summary statistics for human-needed beads
|
||||
|
||||
```
|
||||
bd human
|
||||
bd human [flags]
|
||||
```
|
||||
|
||||
### bd human dismiss
|
||||
|
|
@ -99,5 +99,5 @@ Example:
|
|||
bd human stats
|
||||
|
||||
```
|
||||
bd human stats
|
||||
bd human stats [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ sidebar_position: 0
|
|||
# CLI Reference
|
||||
|
||||
<!-- AUTO-GENERATED: do not edit manually -->
|
||||
Reference for bd Latest. Generated from `bd help --list` and `bd help --doc <command>`.
|
||||
Reference for bd Latest. Generated from `bd help --docs-root`.
|
||||
|
||||
This reference covers all 107 live top-level `bd` commands. Regenerate it with:
|
||||
|
||||
|
|
|
|||
|
|
@ -79,5 +79,5 @@ RECOVERY
|
|||
|
||||
|
||||
```
|
||||
bd init-safety
|
||||
bd init-safety [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Examples:
|
|||
bd jira status # Show sync status
|
||||
|
||||
```
|
||||
bd jira
|
||||
bd jira [flags]
|
||||
```
|
||||
|
||||
### bd jira pull
|
||||
|
|
@ -80,7 +80,7 @@ Show the current Jira sync status, including:
|
|||
- Issues pending push (no external_ref)
|
||||
|
||||
```
|
||||
bd jira status
|
||||
bd jira status [flags]
|
||||
```
|
||||
|
||||
### bd jira sync
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Examples:
|
|||
bd kv list # List all key-value pairs
|
||||
|
||||
```
|
||||
bd kv
|
||||
bd kv [flags]
|
||||
```
|
||||
|
||||
### bd kv clear
|
||||
|
|
@ -34,7 +34,7 @@ Examples:
|
|||
bd kv clear api_endpoint
|
||||
|
||||
```
|
||||
bd kv clear <key>
|
||||
bd kv clear <key> [flags]
|
||||
```
|
||||
|
||||
### bd kv get
|
||||
|
|
@ -46,7 +46,7 @@ Examples:
|
|||
bd kv get api_endpoint
|
||||
|
||||
```
|
||||
bd kv get <key>
|
||||
bd kv get <key> [flags]
|
||||
```
|
||||
|
||||
### bd kv list
|
||||
|
|
@ -58,7 +58,7 @@ Examples:
|
|||
bd kv list --json
|
||||
|
||||
```
|
||||
bd kv list
|
||||
bd kv list [flags]
|
||||
```
|
||||
|
||||
### bd kv set
|
||||
|
|
@ -74,5 +74,5 @@ Examples:
|
|||
bd kv set max_retries 3
|
||||
|
||||
```
|
||||
bd kv set <key> <value>
|
||||
bd kv set <key> <value> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Generated from `bd help --doc label`
|
|||
Manage issue labels
|
||||
|
||||
```
|
||||
bd label
|
||||
bd label [flags]
|
||||
```
|
||||
|
||||
### bd label add
|
||||
|
|
@ -21,7 +21,7 @@ bd label
|
|||
Add a label to one or more issues
|
||||
|
||||
```
|
||||
bd label add [issue-id...] [label]
|
||||
bd label add [issue-id...] [label] [flags]
|
||||
```
|
||||
|
||||
### bd label list
|
||||
|
|
@ -29,7 +29,7 @@ bd label add [issue-id...] [label]
|
|||
List labels for an issue
|
||||
|
||||
```
|
||||
bd label list [issue-id]
|
||||
bd label list [issue-id] [flags]
|
||||
```
|
||||
|
||||
### bd label list-all
|
||||
|
|
@ -37,7 +37,7 @@ bd label list [issue-id]
|
|||
List all unique labels in the database
|
||||
|
||||
```
|
||||
bd label list-all
|
||||
bd label list-all [flags]
|
||||
```
|
||||
|
||||
### bd label propagate
|
||||
|
|
@ -45,7 +45,7 @@ bd label list-all
|
|||
Push a label from a parent down to all direct children that don't already have it. Useful for applying branch: labels across an epic's subtasks.
|
||||
|
||||
```
|
||||
bd label propagate [parent-id] [label]
|
||||
bd label propagate [parent-id] [label] [flags]
|
||||
```
|
||||
|
||||
### bd label remove
|
||||
|
|
@ -53,5 +53,5 @@ bd label propagate [parent-id] [label]
|
|||
Remove a label from one or more issues
|
||||
|
||||
```
|
||||
bd label remove [issue-id...] [label]
|
||||
bd label remove [issue-id...] [label] [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ Examples:
|
|||
bd linear status # Show sync status
|
||||
|
||||
```
|
||||
bd linear
|
||||
bd linear [flags]
|
||||
```
|
||||
|
||||
### bd linear pull
|
||||
|
|
@ -120,7 +120,7 @@ Show the current Linear sync status, including:
|
|||
- Issues pending push (no external_ref)
|
||||
|
||||
```
|
||||
bd linear status
|
||||
bd linear status [flags]
|
||||
```
|
||||
|
||||
### bd linear sync
|
||||
|
|
@ -210,5 +210,5 @@ Example:
|
|||
bd config set linear.team_id "12345678-1234-1234-1234-123456789abc"
|
||||
|
||||
```
|
||||
bd linear teams
|
||||
bd linear teams [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -32,5 +32,5 @@ Examples:
|
|||
bd mail read msg-123 # Reads a message
|
||||
|
||||
```
|
||||
bd mail [subcommand] [args...]
|
||||
bd mail [subcommand] [args...] [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -18,5 +18,5 @@ Examples:
|
|||
bd memories "race flag" # search for a phrase
|
||||
|
||||
```
|
||||
bd memories [search]
|
||||
bd memories [search] [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Examples:
|
|||
bd merge-slot release # Release the slot
|
||||
|
||||
```
|
||||
bd merge-slot
|
||||
bd merge-slot [flags]
|
||||
```
|
||||
|
||||
### bd merge-slot acquire
|
||||
|
|
@ -67,7 +67,7 @@ Returns:
|
|||
- not found: no merge slot exists for this rig
|
||||
|
||||
```
|
||||
bd merge-slot check
|
||||
bd merge-slot check [flags]
|
||||
```
|
||||
|
||||
### bd merge-slot create
|
||||
|
|
@ -78,7 +78,7 @@ The slot ID is automatically generated based on the beads prefix (e.g., gt-merge
|
|||
The slot is created with status=open (available).
|
||||
|
||||
```
|
||||
bd merge-slot create
|
||||
bd merge-slot create [flags]
|
||||
```
|
||||
|
||||
### bd merge-slot release
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Commands:
|
|||
Use "bd formula list" to list available formulas.
|
||||
|
||||
```
|
||||
bd mol
|
||||
bd mol [flags]
|
||||
```
|
||||
|
||||
**Aliases:** protomolecule
|
||||
|
|
@ -233,7 +233,7 @@ Examples:
|
|||
bd mol last-activity hq-wisp-0laki --json
|
||||
|
||||
```
|
||||
bd mol last-activity <molecule-id>
|
||||
bd mol last-activity <molecule-id> [flags]
|
||||
```
|
||||
|
||||
### bd mol pour
|
||||
|
|
@ -297,7 +297,7 @@ Example:
|
|||
bd mol progress bd-hanoi-xyz
|
||||
|
||||
```
|
||||
bd mol progress [molecule-id]
|
||||
bd mol progress [molecule-id] [flags]
|
||||
```
|
||||
|
||||
### bd mol ready
|
||||
|
|
@ -318,7 +318,7 @@ Examples:
|
|||
bd mol ready --gated --json # JSON output for automation
|
||||
|
||||
```
|
||||
bd mol ready --gated
|
||||
bd mol ready --gated [flags]
|
||||
```
|
||||
|
||||
### bd mol seed
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Generated from `bd help --doc notion`
|
|||
Commands for syncing issues between beads and Notion.
|
||||
|
||||
```
|
||||
bd notion
|
||||
bd notion [flags]
|
||||
```
|
||||
|
||||
### bd notion connect
|
||||
|
|
@ -84,7 +84,7 @@ bd notion push [bead-ids...] [flags]
|
|||
Show Notion sync status
|
||||
|
||||
```
|
||||
bd notion status
|
||||
bd notion status [flags]
|
||||
```
|
||||
|
||||
### bd notion sync
|
||||
|
|
|
|||
|
|
@ -27,5 +27,5 @@ For agents or environments that do not auto-inject hook output, use
|
|||
'bd init --agents-profile=full' to embed the complete command reference.
|
||||
|
||||
```
|
||||
bd onboard
|
||||
bd onboard [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -25,5 +25,5 @@ Examples:
|
|||
bd ping --json # Structured output for automation
|
||||
|
||||
```
|
||||
bd ping
|
||||
bd ping [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -26,5 +26,5 @@ Examples:
|
|||
bd priority bd-123 2 # Medium
|
||||
|
||||
```
|
||||
bd priority <id> <n>
|
||||
bd priority <id> <n> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -13,5 +13,5 @@ Generated from `bd help --doc quickstart`
|
|||
Display a quick start guide showing common bd workflows and patterns.
|
||||
|
||||
```
|
||||
bd quickstart
|
||||
bd quickstart [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -17,5 +17,5 @@ Examples:
|
|||
bd recall auth-jwt
|
||||
|
||||
```
|
||||
bd recall <key>
|
||||
bd recall <key> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -29,5 +29,5 @@ Examples:
|
|||
bd recompute-blocked --json # Machine-parseable {"rows_corrected": N}
|
||||
|
||||
```
|
||||
bd recompute-blocked
|
||||
bd recompute-blocked [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -25,5 +25,5 @@ Examples:
|
|||
Note: The new ID must use a valid prefix for this database.
|
||||
|
||||
```
|
||||
bd rename <old-id> <new-id>
|
||||
bd rename <old-id> <new-id> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ Examples:
|
|||
bd repo sync # Sync from all configured repos
|
||||
|
||||
```
|
||||
bd repo
|
||||
bd repo [flags]
|
||||
```
|
||||
|
||||
### bd repo add
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Generated from `bd help --doc rules`
|
|||
Audit and compact Claude rules
|
||||
|
||||
```
|
||||
bd rules
|
||||
bd rules [flags]
|
||||
```
|
||||
|
||||
### bd rules audit
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ Examples:
|
|||
bd state witness-abc health # Output: healthy
|
||||
|
||||
```
|
||||
bd state <issue-id> <dimension>
|
||||
bd state <issue-id> <dimension> [flags]
|
||||
```
|
||||
|
||||
### bd state list
|
||||
|
|
@ -42,5 +42,5 @@ Example:
|
|||
# health: healthy
|
||||
|
||||
```
|
||||
bd state list <issue-id>
|
||||
bd state list <issue-id> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -31,5 +31,5 @@ Examples:
|
|||
|
||||
|
||||
```
|
||||
bd statuses
|
||||
bd statuses [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ A swarm is a structured body of work defined by an epic and its children,
|
|||
with dependencies forming a DAG (directed acyclic graph) of work.
|
||||
|
||||
```
|
||||
bd swarm
|
||||
bd swarm [flags]
|
||||
```
|
||||
|
||||
### bd swarm create
|
||||
|
|
@ -63,7 +63,7 @@ Examples:
|
|||
bd swarm list --json # Machine-readable output
|
||||
|
||||
```
|
||||
bd swarm list
|
||||
bd swarm list [flags]
|
||||
```
|
||||
|
||||
### bd swarm status
|
||||
|
|
@ -89,7 +89,7 @@ Examples:
|
|||
bd swarm status gt-epic-123 --json # Machine-readable output
|
||||
|
||||
```
|
||||
bd swarm status [epic-or-swarm-id]
|
||||
bd swarm status [epic-or-swarm-id] [flags]
|
||||
```
|
||||
|
||||
### bd swarm validate
|
||||
|
|
|
|||
|
|
@ -19,5 +19,5 @@ Examples:
|
|||
bd tag bd-123 needs-review
|
||||
|
||||
```
|
||||
bd tag <id> <label>
|
||||
bd tag <id> <label> [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ TODOs can be promoted to full issues by changing type or priority:
|
|||
bd update todo-123 --type bug --priority 0
|
||||
|
||||
```
|
||||
bd todo
|
||||
bd todo [flags]
|
||||
```
|
||||
|
||||
### bd todo add
|
||||
|
|
|
|||
|
|
@ -21,5 +21,5 @@ Examples:
|
|||
|
||||
|
||||
```
|
||||
bd types
|
||||
bd types [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -20,5 +20,5 @@ Examples:
|
|||
bd undefer bd-abc bd-def # Undefer multiple issues
|
||||
|
||||
```
|
||||
bd undefer [id...]
|
||||
bd undefer [id...] [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ The upgrade command helps you stay aware of bd version changes:
|
|||
Version tracking is automatic - bd updates metadata.json on every run.
|
||||
|
||||
```
|
||||
bd upgrade
|
||||
bd upgrade [flags]
|
||||
```
|
||||
|
||||
### bd upgrade ack
|
||||
|
|
@ -39,7 +39,7 @@ Examples:
|
|||
bd upgrade ack --json
|
||||
|
||||
```
|
||||
bd upgrade ack
|
||||
bd upgrade ack [flags]
|
||||
```
|
||||
|
||||
### bd upgrade review
|
||||
|
|
@ -57,7 +57,7 @@ Examples:
|
|||
bd upgrade review --json
|
||||
|
||||
```
|
||||
bd upgrade review
|
||||
bd upgrade review [flags]
|
||||
```
|
||||
|
||||
### bd upgrade status
|
||||
|
|
@ -72,5 +72,5 @@ Examples:
|
|||
bd upgrade status --json
|
||||
|
||||
```
|
||||
bd upgrade status
|
||||
bd upgrade status [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Note: 'bd history', 'bd diff', and 'bd branch' also work for quick access.
|
|||
This subcommand provides additional operations like merge and commit.
|
||||
|
||||
```
|
||||
bd vc
|
||||
bd vc [flags]
|
||||
```
|
||||
|
||||
### bd vc commit
|
||||
|
|
@ -72,5 +72,5 @@ Examples:
|
|||
bd vc status
|
||||
|
||||
```
|
||||
bd vc status
|
||||
bd vc status [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -13,5 +13,5 @@ Generated from `bd help --doc version`
|
|||
Print version information
|
||||
|
||||
```
|
||||
bd version
|
||||
bd version [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -21,5 +21,5 @@ Examples:
|
|||
|
||||
|
||||
```
|
||||
bd where
|
||||
bd where [flags]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Examples:
|
|||
bd worktree info # Show info about current worktree
|
||||
|
||||
```
|
||||
bd worktree
|
||||
bd worktree [flags]
|
||||
```
|
||||
|
||||
### bd worktree create
|
||||
|
|
@ -70,7 +70,7 @@ Examples:
|
|||
bd worktree info --json # JSON output
|
||||
|
||||
```
|
||||
bd worktree info
|
||||
bd worktree info [flags]
|
||||
```
|
||||
|
||||
### bd worktree list
|
||||
|
|
@ -88,7 +88,7 @@ Examples:
|
|||
bd worktree list --json # JSON output
|
||||
|
||||
```
|
||||
bd worktree list
|
||||
bd worktree list [flags]
|
||||
```
|
||||
|
||||
### bd worktree remove
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue