* docs(pipeline): pin the generated CLI docs to the released bd; repair main's CLI reference The #4874 squash-merge raced the docs-autofix bot: the bot had pushed a regeneration from main's source onto the PR branch, so the squash landed a contradictory mix — the release-aligned hand-written docs plus a CLI reference re-documenting unreleased commands and flags, with docs.json referencing four pages (heartbeat, migrate-personal, reclaim, unclaim) whose files do not exist. That broken nav fails the docsync guard on main and on every branch cut from it. This restores the intended end state of #4874 and lands the pin that prevents the race from recurring. - Regenerate the CLI reference from a bd built from the v1.1.0 tag (CI's canonical pure-Go build), removing the unreleased commands/flags and fixing the dangling nav entries. - docs/cli-docs.pin names the release tag; scripts/resolve-docs-bd.sh builds and caches a canonical pure-Go bd from that tag, fetching the tag first in shallow CI checkouts. - generate-cli-docs.sh, check-doc-flags.sh, and check-cli-docs-drift.sh resolve bd through the pin and ignore a supplied binary while pinned (BD_DOCS_IGNORE_PIN=1 bypasses), so the drift gates and the autofix bot now enforce docs-match-release instead of docs-match-main. - tools/docsmint detects the pre-overhaul Docusaurus staging layout that bd <= v1.1.0 emits and converts it to the generic form before its normal Mintlify transform (tested); removable once the pin reaches a release whose emitter writes build/cli-docs. - check-doc-flags.sh: run without timeout(1) on macOS instead of failing Check 4. - Decision record: engdocs/decisions/2026-07-17-docs-release-pin.md; the beads-docs skill §8 updated to match. * lint: annotate gosec G705 false positive in the docsmint legacy bridge Same class as the existing nav-splice annotation: a developer tool writing repo Markdown, not a web-output sink.
50 lines
1.9 KiB
Markdown
50 lines
1.9 KiB
Markdown
---
|
|
title: "bd find-duplicates"
|
|
description: "Find issues that are semantically similar but not exact duplicates."
|
|
---
|
|
|
|
{/* AUTO-GENERATED: do not edit manually */}
|
|
|
|
Generated from `bd help --doc find-duplicates`.
|
|
|
|
Find issues that are semantically similar but not exact duplicates.
|
|
|
|
Unlike 'bd duplicates' which finds exact content matches, find-duplicates
|
|
uses text similarity or AI to find issues that discuss the same topic
|
|
with different wording.
|
|
|
|
Approaches:
|
|
mechanical Token-based text similarity (default, no API key needed)
|
|
ai LLM-based semantic comparison (requires ANTHROPIC_API_KEY or ai.api_key)
|
|
|
|
The mechanical approach tokenizes titles and descriptions, then computes
|
|
Jaccard similarity between all issue pairs. It's fast and free but may
|
|
miss semantically similar issues with very different wording.
|
|
|
|
The AI approach sends candidate pairs to Claude for semantic comparison.
|
|
It first uses mechanical pre-filtering to reduce the number of API calls,
|
|
then asks the LLM to judge whether the remaining pairs are true duplicates.
|
|
|
|
Examples:
|
|
bd find-duplicates # Mechanical similarity (default)
|
|
bd find-duplicates --threshold 0.4 # Lower threshold = more results
|
|
bd find-duplicates --method ai # Use AI for semantic comparison
|
|
bd find-duplicates --status open # Only check open issues
|
|
bd find-duplicates --limit 20 # Show top 20 pairs
|
|
bd find-duplicates --json # JSON output
|
|
|
|
```
|
|
bd find-duplicates [flags]
|
|
```
|
|
|
|
**Aliases:** find-dups
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
-n, --limit int Maximum number of pairs to show (default 50)
|
|
--method string Detection method: mechanical, ai (default "mechanical")
|
|
--model string AI model to use (only with --method ai; default from config ai.model)
|
|
-s, --status string Filter by status (default: non-closed)
|
|
--threshold float Similarity threshold (0.0-1.0, lower = more results) (default 0.5)
|
|
```
|