* docs: generate CLI reference from live help * docs(cli): move bd version stamp from per-command pages to index only Drops the `(bd version X.Y.Z)` suffix from the auto-generated header on every per-command CLI reference page (writeSingleCommandDoc) and the docs/CLI_REFERENCE.md preamble (writeAllHelp). The version label now lives only on the index page emitted by scripts/generate-cli-docs.sh: - Dev tree (website/docs/cli-reference/index.md, docs/CLI_REFERENCE.md): labelled "Latest" - Versioned snapshots (website/versioned_docs/version-X.Y.Z/...): labelled with the explicit semver tag parsed from the directory name This eliminates the 100+-file no-signal diff a release version bump otherwise produces, restoring the "regen as a separate small commit" workflow PR #3704 enables. After this change a version bump alone yields zero diff on the dev tree; only the new versioned snapshot created at release-cut time carries the new tag. No datestamps are introduced anywhere — scripts/generate-cli-docs.sh --check remains deterministic across CI runs. Refs: mybd-afb, PR #3704 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: CI Bot <ci@beads.test> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
103 lines
2.1 KiB
Markdown
103 lines
2.1 KiB
Markdown
---
|
|
id: human
|
|
title: bd human
|
|
slug: /cli-reference/human
|
|
sidebar_position: 999
|
|
---
|
|
|
|
<!-- AUTO-GENERATED: do not edit manually -->
|
|
Generated from `bd help --doc human`
|
|
|
|
## bd human
|
|
|
|
Display a focused help menu showing only the most common commands.
|
|
|
|
bd has 70+ commands - many for AI agents, integrations, and advanced workflows.
|
|
This command shows the ~15 essential commands that human users need most often.
|
|
|
|
For the full command list, run: bd --help
|
|
|
|
SUBCOMMANDS:
|
|
human list List all human-needed beads (issues with 'human' label)
|
|
human respond <id> Respond to a human-needed bead (adds comment and closes)
|
|
human dismiss <id> Dismiss a human-needed bead permanently
|
|
human stats Show summary statistics for human-needed beads
|
|
|
|
```
|
|
bd human
|
|
```
|
|
|
|
### bd human dismiss
|
|
|
|
Dismiss a human-needed bead permanently without responding.
|
|
|
|
The issue is closed with a "Dismissed" reason and optional note.
|
|
|
|
Examples:
|
|
bd human dismiss bd-123
|
|
bd human dismiss bd-123 --reason "No longer applicable"
|
|
|
|
```
|
|
bd human dismiss <issue-id> [flags]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
--reason string Reason for dismissal (optional)
|
|
```
|
|
|
|
### bd human list
|
|
|
|
List all issues labeled with 'human' tag.
|
|
|
|
These are issues that require human intervention or input.
|
|
|
|
Examples:
|
|
bd human list
|
|
bd human list --status=open
|
|
bd human list --json
|
|
|
|
```
|
|
bd human list [flags]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
-s, --status string Filter by status (open, closed, etc.)
|
|
```
|
|
|
|
### bd human respond
|
|
|
|
Respond to a human-needed bead by adding a comment and closing it.
|
|
|
|
The response is added as a comment and the issue is closed with reason "Responded".
|
|
|
|
Examples:
|
|
bd human respond bd-123 --response "Use OAuth2 for authentication"
|
|
bd human respond bd-123 -r "Approved, proceed with implementation"
|
|
|
|
```
|
|
bd human respond <issue-id> [flags]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
-r, --response string Response text (required)
|
|
```
|
|
|
|
### bd human stats
|
|
|
|
Display summary statistics for human-needed beads.
|
|
|
|
Shows counts for total, pending (open), responded (closed without dismiss),
|
|
and dismissed beads.
|
|
|
|
Example:
|
|
bd human stats
|
|
|
|
```
|
|
bd human stats
|
|
```
|