Three generated-content defects from the adversarial review, all structurally invisible to the drift gate (generated-vs-generated): - Usage lines now mirror Cobra's help template: a runnable command shows its UseLine, a command with subcommands shows '<path> [command]', both when both apply. Previously bare UseLine() stamped 'bd mol [flags]' on 30 parent pages — a line the binary never prints. - The generated CLI index publishes the Global Flags block; the binary prints it on every --help but no page carried it. - docsmint neutralizes prose lines that Mintlify's prebuild would dedent into MDX ESM blocks (a line beginning 'export'/'import' outside a fence gets wrapped in a code span). This is why /cli-reference/mail returned HTTP 200 while rendering only a parse-error placeholder — reproduced, fixed, and covered by a planted-hazard test; fenced content stays verbatim. Also rewords check-cli-docs-drift.sh's early-PASS message, which asserted 'the supplied binary differs' as the cause when uncommitted local edits produce the same result. All 113 pages + docs/CLI_REFERENCE.md regenerated through the pipeline; TDD'd in cmd/bd/help_all_test.go and tools/docsmint/docsmint_test.go. Verified live: /cli-reference/mail renders real content, zero parse errors; generate-cli-docs.sh --check, docsync, freshness, and mint broken-links all pass on this tree.
101 lines
2.1 KiB
Markdown
101 lines
2.1 KiB
Markdown
---
|
|
title: "bd human"
|
|
description: "Show essential commands for human users"
|
|
---
|
|
|
|
{/* AUTO-GENERATED: do not edit manually */}
|
|
|
|
Generated from `bd help --doc 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 [flags]
|
|
bd human [command]
|
|
```
|
|
|
|
## 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 [flags]
|
|
```
|