boost-skill-cli 1.0.148__tar.gz → 1.0.149__tar.gz

{boost_skill_cli-1.0.148 → boost_skill_cli-1.0.149}/Makefile

@@ -10,7 +10,7 @@ PYTEST    := $(VENV)/bin/pytest
 # pinned taps out of the developer's real ~/.boost.
 EVAL_HOME := $(CURDIR)/.eval-home
 
-.PHONY: venv test unit functional smoke coverage mutation lint check demo clean-test eval eval-ai eval-rec eval-stats eval-explain audit dist-check
+.PHONY: venv test unit functional smoke coverage mutation lint check demo clean-test eval eval-ai eval-rec eval-stats eval-explain audit dist-check bdd bench bench-cli
 
 venv:
 	python3 -m venv $(VENV)
@@ -96,6 +96,24 @@ eval-explain:
 	PYTHON=$(PY) BOOST_HOME=$(EVAL_HOME) bash scripts/ensure_eval_corpus.sh
 	BOOST_HOME=$(EVAL_HOME) $(PY) scripts/eval_explain.py --fail-under 0.80
 
+# Opt-in Gherkin/BDD suite (tests/bdd) — additive to tests/functional, not a
+# replacement. Needs the [bdd] extra (`pip install -e '.[bdd]'`); not part of
+# `make check`.
+bdd:
+	$(VENV)/bin/behave tests/bdd/features
+
+# Opt-in micro-benchmarks (tests/perf) for perf-sensitive core paths. Needs
+# the [perf] extra (`pip install -e '.[perf]'`); not part of `make check` — a
+# timing regression is informational, not a merge gate.
+bench:
+	$(PYTEST) tests/perf --benchmark-only -q
+
+# Opt-in wall-clock benchmark of the real `boost` binary via hyperfine. Not
+# part of `make check`; degrades cleanly (prints a skip message, exits 0) when
+# hyperfine isn't installed (`brew install hyperfine`).
+bench-cli:
+	@command -v hyperfine >/dev/null 2>&1 && bash scripts/bench_cli.sh || echo "hyperfine not on PATH — install via 'brew install hyperfine', skipping"
+
 # regenerate generated artifacts from their source (registries + roadmap boards)
 generate:
 	$(PY) scripts/build_registries.py

{boost_skill_cli-1.0.148 → boost_skill_cli-1.0.149}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.148
+Version: 1.0.149
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE
@@ -708,6 +708,10 @@ Requires-Dist: ragas<0.3,>=0.2; extra == "eval"
 Requires-Dist: langchain-core<0.4; extra == "eval"
 Requires-Dist: langchain-community<0.4; extra == "eval"
 Requires-Dist: langchain-openai<1; extra == "eval"
+Provides-Extra: bdd
+Requires-Dist: behave>=1.2.6; extra == "bdd"
+Provides-Extra: perf
+Requires-Dist: pytest-benchmark>=4.0; extra == "perf"
 Dynamic: license-file
 
 # boost — a package manager for AI coding skills

{boost_skill_cli-1.0.148 → boost_skill_cli-1.0.149}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.0.148'
-__version_tuple__ = version_tuple = (1, 0, 148)
+__version__ = version = '1.0.149'
+__version_tuple__ = version_tuple = (1, 0, 149)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.0.148 → boost_skill_cli-1.0.149}/boost_skill_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.148
+Version: 1.0.149
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE
@@ -708,6 +708,10 @@ Requires-Dist: ragas<0.3,>=0.2; extra == "eval"
 Requires-Dist: langchain-core<0.4; extra == "eval"
 Requires-Dist: langchain-community<0.4; extra == "eval"
 Requires-Dist: langchain-openai<1; extra == "eval"
+Provides-Extra: bdd
+Requires-Dist: behave>=1.2.6; extra == "bdd"
+Provides-Extra: perf
+Requires-Dist: pytest-benchmark>=4.0; extra == "perf"
 Dynamic: license-file
 
 # boost — a package manager for AI coding skills

{boost_skill_cli-1.0.148 → boost_skill_cli-1.0.149}/boost_skill_cli.egg-info/SOURCES.txt

@@ -217,6 +217,7 @@ docs/roadmap/items/workspace-scope-install.md
 examples/README.md
 examples/adapt-demo.sh
 examples/boost-run-prototype.sh
+scripts/bench_cli.sh
 scripts/build_registries.py
 scripts/build_roadmap.py
 scripts/ensure_eval_corpus.sh
@@ -231,6 +232,22 @@ style/demo.html
 tests/conftest.py
 tests/make_fixture.py
 tests/smoke.sh
+tests/bdd/features/adapt.feature
+tests/bdd/features/browse.feature
+tests/bdd/features/count.feature
+tests/bdd/features/discover.feature
+tests/bdd/features/doctor.feature
+tests/bdd/features/environment.py
+tests/bdd/features/explain.feature
+tests/bdd/features/index.feature
+tests/bdd/features/install.feature
+tests/bdd/features/list.feature
+tests/bdd/features/mcp.feature
+tests/bdd/features/search.feature
+tests/bdd/features/steps/cli_steps.py
+tests/bdd/features/steps/discovery_steps.py
+tests/bdd/features/steps/mcp_steps.py
+tests/bdd/features/steps/quality_steps.py
 tests/eval/baseline.json
 tests/eval/explain.jsonl
 tests/eval/golden.jsonl
@@ -249,6 +266,7 @@ tests/functional/test_cli_taps.py
 tests/functional/test_cli_team.py
 tests/functional/test_everyday_loop.py
 tests/functional/test_property_parsers.py
+tests/perf/test_benchmarks.py
 tests/unit/test_adapters.py
 tests/unit/test_agents.py
 tests/unit/test_ai.py

{boost_skill_cli-1.0.148 → boost_skill_cli-1.0.149}/boost_skill_cli.egg-info/requires.txt

@@ -1,4 +1,7 @@
 
+[bdd]
+behave>=1.2.6
+
 [eval]
 ranx>=0.3.20
 ragas<0.3,>=0.2
@@ -6,5 +9,8 @@ langchain-core<0.4
 langchain-community<0.4
 langchain-openai<1
 
+[perf]
+pytest-benchmark>=4.0
+
 [rag]
 sqlite-vec>=0.1.6

{boost_skill_cli-1.0.148 → boost_skill_cli-1.0.149}/pyproject.toml

@@ -55,6 +55,16 @@ eval = [
     "langchain-community<0.4",
     "langchain-openai<1",
 ]
+# Opt-in Gherkin/BDD functional suite (tests/bdd) — reusable Given/When/Then
+# scenarios over the same in-process CLI entrypoint tests/functional drives.
+# Additive to, not a replacement for, the pytest functional suite; not part of
+# `make check`. `pip install -e '.[bdd]'`.
+bdd = ["behave>=1.2.6"]
+# Opt-in micro-benchmarks (tests/perf, `make bench`) for perf-sensitive core
+# paths (BM25 indexing/search, catalog scan). Not part of `make check` — a
+# timing regression shouldn't block a merge the way a correctness gate does.
+# `pip install -e '.[perf]'`.
+perf = ["pytest-benchmark>=4.0"]
 
 [project.scripts]
 boost = "boost_cli.cli:main"

boost_skill_cli-1.0.149/scripts/bench_cli.sh

@@ -0,0 +1,27 @@
+#!/usr/bin/env bash
+# Wall-clock benchmark of the real `boost` binary via hyperfine — the actual
+# fork+exec CLI, not the in-process pytest-benchmark suite (tests/perf).
+# Opt-in (`make bench-cli`); not part of `make check`. Degrades cleanly if
+# hyperfine isn't installed.
+set -uo pipefail
+
+if ! command -v hyperfine >/dev/null 2>&1; then
+  echo "hyperfine not installed — install via 'brew install hyperfine', skipping"
+  exit 0
+fi
+
+ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+SB="$(mktemp -d "${TMPDIR:-/tmp}/boost-bench-XXXXXX")"
+trap 'rm -rf "$SB"' EXIT
+export HOME="$SB" BOOST_NO_AI=1 BOOST_ASSUME_YES=1 NO_COLOR=1
+
+FIX="$(python3 "$ROOT/tests/make_fixture.py" "$SB/fixture-tap")"
+"$ROOT/boost" tap "$FIX" >/dev/null
+"$ROOT/boost" install brainstorming >/dev/null
+
+echo "== hyperfine: $(command -v hyperfine) over $ROOT/boost (sandbox: $SB)"
+hyperfine --warmup 3 \
+  "$ROOT/boost --help" \
+  "$ROOT/boost list" \
+  "$ROOT/boost search brainstorming" \
+  "$ROOT/boost count"

boost_skill_cli-1.0.149/tests/bdd/features/adapt.feature

@@ -0,0 +1,46 @@
+Feature: boost adapt
+  Render a skill as another agent framework's native source (CrewAI, Agents SDK).
+
+  Background:
+    Given a fresh boost environment
+    And the fixture tap is added
+
+  Scenario: adapting an installed skill to CrewAI
+    Given the "brainstorming" skill is installed
+    When I run "boost adapt brainstorming --to crewai"
+    Then the exit code should be 0
+    And the output should contain "from crewai import Agent"
+    And the output should contain "brainstorming = Agent("
+
+  Scenario: adapting an installed skill to the Agents SDK
+    Given the "brainstorming" skill is installed
+    When I run "boost adapt brainstorming --to agents-sdk"
+    Then the exit code should be 0
+    And the output should contain "from agents import Agent"
+    And the output should match "name=\"brainstorming\""
+
+  Scenario: adapting a tapped-but-not-installed skill still resolves
+    When I run "boost adapt brainstorming --to crewai"
+    Then the exit code should be 0
+    And the output should contain "brainstorming = Agent("
+
+  Scenario: --model none opts out of pinning an LLM
+    Given the "brainstorming" skill is installed
+    When I run "boost adapt brainstorming --to crewai --model none"
+    Then the exit code should be 0
+    And the output should not contain "llm="
+
+  Scenario: an unknown framework is rejected
+    Given the "brainstorming" skill is installed
+    When I run "boost adapt brainstorming --to langchain"
+    Then the exit code should be 1
+    And the output should contain "unknown framework"
+
+  Scenario: --to is required
+    Given the "brainstorming" skill is installed
+    When I run "boost adapt brainstorming"
+    Then the exit code should be 2
+
+  Scenario: adapting an unknown skill fails
+    When I run "boost adapt does-not-exist --to crewai"
+    Then the exit code should be 1

boost_skill_cli-1.0.149/tests/bdd/features/browse.feature

@@ -0,0 +1,26 @@
+Feature: boost browse
+  Interactive full-screen TUI with fuzzy search. There is no TTY in these
+  scenarios, so `browse` takes its documented non-interactive escape hatch
+  and prints the full catalog instead of launching curses.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: no skills available to browse
+    When I run "boost browse"
+    Then the exit code should be 1
+    And the output should contain "no skills available to browse"
+
+  Scenario: without a TTY, prints the full catalog instead of the TUI
+    Given the fixture tap is added
+    When I run "boost browse"
+    Then the exit code should be 0
+    And the output should contain "interactive mode needs a TTY — showing the full catalog"
+    And the output should contain "brainstorming"
+    And the output should contain "commit-messages"
+    And the output should contain "5 skills · install with `boost install <name>`"
+
+  Scenario: --help documents the command without touching the catalog
+    When I run "boost browse --help"
+    Then the exit code should be 0
+    And the output should contain "Interactive full-screen TUI with fuzzy search"

boost_skill_cli-1.0.149/tests/bdd/features/count.feature

@@ -0,0 +1,24 @@
+Feature: boost count
+  A one-line inventory summary: installed / available / taps / discovery index.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: an empty environment
+    When I run "boost count"
+    Then the exit code should be 0
+    And the output should contain "installed 0 · available 0 (across 0 taps) · discovery index not built"
+
+  Scenario: one tap with one installed skill
+    Given the "brainstorming" skill is installed
+    When I run "boost count"
+    Then the exit code should be 0
+    And the output should contain "installed 1 · available 5 (across 1 tap) · discovery index not built"
+    And the output should contain "╭─ inventory"
+
+  Scenario: --json is machine readable
+    Given the "brainstorming" skill is installed
+    When I run "boost count --json"
+    Then the exit code should be 0
+    And the output should match "\"installed\": 1"
+    And the output should match "\"taps\": 1"

boost_skill_cli-1.0.149/tests/bdd/features/discover.feature

@@ -0,0 +1,39 @@
+Feature: boost discover
+  Browse and filter the GitHub-wide discovery index built by `boost index`.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: without an index and without gh, hints to install gh
+    Given the GitHub CLI is not installed
+    When I run "boost discover"
+    Then the exit code should be 0
+    And the output should contain "the discovery index has not been built yet"
+    And the output should contain "install the GitHub CLI first"
+
+  Scenario: without an index but with gh, hints to run boost index
+    Given the GitHub CLI is installed and code search returns 2 sample skill files
+    When I run "boost discover"
+    Then the exit code should be 0
+    And the output should contain "build it with `boost index` (GitHub Code Search)"
+
+  Scenario: a query filters indexed entries
+    Given the discovery index is seeded with sample items
+    When I run "boost discover acme"
+    Then the exit code should be 0
+    And the output should contain "skills/web/SKILL.md"
+    And the output should not contain "octo/skills"
+    And the output should contain "2 of 3 indexed skills · GitHub reports ~42 total"
+
+  Scenario: a query with no matches reports the index size
+    Given the discovery index is seeded with sample items
+    When I run "boost discover zzz"
+    Then the exit code should be 0
+    And the output should contain "no indexed skills match 'zzz'"
+    And the output should contain "the index holds 3 entries — rebuild with `boost index`"
+
+  Scenario: a corrupt index fails cleanly
+    Given the discovery index is corrupt
+    When I run "boost discover"
+    Then the exit code should be 1
+    And the output should contain "the discovery index is corrupt"

boost_skill_cli-1.0.149/tests/bdd/features/doctor.feature

@@ -0,0 +1,30 @@
+Feature: boost doctor
+  Check installation health and report issues.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: an empty environment is healthy
+    When I run "boost doctor"
+    Then the exit code should be 0
+    And the output should contain "boost doctor"
+    And the output should contain "no taps configured — add one with `boost tap owner/repo`"
+    And the output should contain "0 skills installed · 0 taps synced · 0 broken links"
+
+  Scenario: a healthy environment with installed skills
+    Given the "brainstorming" skill is installed
+    When I run "boost doctor"
+    Then the exit code should be 0
+    And the output should contain "git on PATH"
+    And the output should contain "1 tap cloned & cached"
+    And the output should contain "1 skill installed · 1 tap synced · 0 broken links"
+    And the output should contain "● healthy"
+
+  Scenario: a broken symlink is reported and flips the verdict
+    Given the "brainstorming" skill is installed
+    And a broken skill symlink exists
+    When I run "boost doctor"
+    Then the exit code should be 1
+    And the output should contain "1 broken symlink in agent dirs — run `boost heal`"
+    And the output should contain "need attention"
+

boost_skill_cli-1.0.149/tests/bdd/features/environment.py

@@ -0,0 +1,66 @@
+"""behave hooks — mirrors tests/conftest.py's sandboxing for BDD scenarios.
+
+Every scenario runs against a throwaway $HOME (never the real one) and shares
+one fixture tap built once per run via tests/make_fixture.py.
+"""
+from __future__ import annotations
+
+import os
+import shutil
+import subprocess
+import sys
+import tempfile
+from pathlib import Path
+
+ROOT = Path(__file__).resolve().parents[3]
+if str(ROOT) not in sys.path:
+    sys.path.insert(0, str(ROOT))
+
+_SANDBOX_ENV = ("BOOST_HOME", "BOOST_AGENTS_STORE", "BOOST_DEBUG",
+                "BOOST_LOG_LEVEL", "BOOST_NO_LOG", "VOYAGE_API_KEY",
+                "OPENAI_API_KEY", "BOOST_NO_EMBED")
+
+
+def before_all(context):
+    context._run_dir = Path(tempfile.mkdtemp(prefix="boost-bdd-"))
+    dest = context._run_dir / "fixture-tap"
+    subprocess.run(
+        [sys.executable, str(ROOT / "tests" / "make_fixture.py"), str(dest)],
+        check=True, capture_output=True)
+    context.fixture_tap_src = dest
+
+
+_scenario_counter = [0]
+
+
+def before_scenario(context, scenario):
+    context._saved_env = dict(os.environ)
+    _scenario_counter[0] += 1
+    home = context._run_dir / ("home-%d" % _scenario_counter[0])
+    home.mkdir(parents=True, exist_ok=True)
+    os.environ["HOME"] = str(home)
+    for var in _SANDBOX_ENV:
+        os.environ.pop(var, None)
+    os.environ["BOOST_NO_AI"] = "1"       # deterministic: no AI calls
+    os.environ["NO_COLOR"] = "1"          # plain output for assertions
+    os.environ["BOOST_ASSUME_YES"] = "1"  # never block on confirm()
+    context._home = home
+    context._tapped = False
+    context._patchers = []
+
+    from boost_cli.core import logs
+    logs.reset()
+
+
+def after_scenario(context, scenario):
+    for patcher in reversed(context._patchers):
+        patcher.stop()
+    context._patchers = []
+    from boost_cli.core import logs
+    logs.reset()
+    os.environ.clear()
+    os.environ.update(context._saved_env)
+
+
+def after_all(context):
+    shutil.rmtree(context._run_dir, ignore_errors=True)

boost_skill_cli-1.0.149/tests/bdd/features/explain.feature

@@ -0,0 +1,25 @@
+Feature: boost explain
+  Explain what a skill does in plain English (falls back to a heuristic
+  summary when AI is unavailable — the sandbox always sets BOOST_NO_AI=1).
+
+  Background:
+    Given a fresh boost environment
+    And the fixture tap is added
+
+  Scenario: explaining an installed skill without AI uses the heuristic fallback
+    Given the "brainstorming" skill is installed
+    When I run "boost explain brainstorming"
+    Then the exit code should be 0
+    And the output should contain "using the heuristic fallback"
+    And the output should contain "Outline:"
+    And the output should contain "Key rules:"
+
+  Scenario: explaining a skill that is only in a tap (not installed)
+    When I run "boost explain jira-integration"
+    Then the exit code should be 0
+    And the output should contain "using the heuristic fallback"
+
+  Scenario: explaining an unknown skill fails
+    When I run "boost explain does-not-exist"
+    Then the exit code should be 1
+    And the output should contain "no skill named 'does-not-exist' in any tap"

boost_skill_cli-1.0.149/tests/bdd/features/index.feature

@@ -0,0 +1,25 @@
+Feature: boost index
+  Build the discovery registry via GitHub Code Search. `gh` is always
+  mocked in these scenarios — no real network call.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: requires the GitHub CLI
+    Given the GitHub CLI is not installed
+    When I run "boost index"
+    Then the exit code should be 1
+    And the output should contain "the GitHub CLI (gh) is required to build the index"
+    And the output should contain "brew install gh"
+
+  Scenario: builds the cache from gh's JSON output
+    Given the GitHub CLI is installed and code search returns 2 sample skill files
+    When I run "boost index --limit 100"
+    Then the exit code should be 0
+    And the output should contain "indexed 2 skill files across 2 repos (GitHub reports 7 total)"
+
+  Scenario: a gh failure on the first page aborts with an error
+    Given the GitHub CLI is installed but code search fails
+    When I run "boost index --limit 50"
+    Then the exit code should be 1
+    And the output should contain "GitHub code search failed"

boost_skill_cli-1.0.149/tests/bdd/features/install.feature

@@ -0,0 +1,43 @@
+Feature: boost install
+  Install a skill from a tap registry into the local store and link it into
+  every enabled agent.
+
+  Background:
+    Given a fresh boost environment
+    And the fixture tap is added
+
+  Scenario: installing a known skill links it into every agent
+    When I run "boost install brainstorming"
+    Then the exit code should be 0
+    And the output should contain "copied to ~/.agents/skills/brainstorming"
+    And the output should contain "linked → claude-code · windsurf · cursor"
+    And the output should contain "Installed 1 new skill; quality score 95/100"
+    And the output should contain "next: boost info brainstorming"
+
+  Scenario: --dry-run changes nothing on disk
+    When I run "boost install brainstorming --dry-run"
+    Then the exit code should be 0
+    And the output should contain "would install brainstorming v1.4.0 from fixture-tap"
+    And the output should contain "dry run — nothing was changed"
+
+  Scenario: --agent restricts linking to a single agent
+    When I run "boost install brainstorming --agent claude-code"
+    Then the exit code should be 0
+    And the output should contain "linked → claude-code"
+    And the output should not contain "windsurf"
+
+  Scenario: an unknown agent is rejected
+    When I run "boost install brainstorming --agent emacs"
+    Then the exit code should be 1
+    And the output should contain "unknown agent: emacs"
+
+  Scenario: installing an unknown skill fails with a hint
+    When I run "boost install does-not-exist"
+    Then the exit code should be 1
+    And the output should contain "no skill named 'does-not-exist' in any tap"
+
+  Scenario: a mix of known and unknown skills installs the known ones
+    When I run "boost install brainstorming nope"
+    Then the exit code should be 1
+    And the output should contain "nope: no skill named 'nope' in any tap"
+    And the output should contain "Installed 1 new skill; quality score 95/100"

boost_skill_cli-1.0.149/tests/bdd/features/list.feature

@@ -0,0 +1,42 @@
+Feature: boost list
+  List installed skills, rules, and workflows.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: no skills installed shows an empty state
+    When I run "boost list"
+    Then the exit code should be 0
+    And the output should contain "no skills installed"
+    And the output should contain "boost tap --defaults"
+
+  Scenario: an installed skill is listed with its version and tap
+    Given the "brainstorming" skill is installed
+    When I run "boost list"
+    Then the exit code should be 0
+    And the output should contain "installed skills"
+    And the output should contain "brainstorming"
+    And the output should contain "1.4.0"
+    And the output should contain "fixture-tap"
+    And the output should contain "1 skill installed"
+
+  Scenario: --json is machine readable
+    Given the "brainstorming" skill is installed
+    When I run "boost list --json"
+    Then the exit code should be 0
+    And the output should match "\"brainstorming\""
+    And the output should match "\"skills\""
+
+  Scenario: --tag narrows the listing to custom-tagged skills
+    Given the "brainstorming" skill is installed
+    When I run "boost tag brainstorming +fav"
+    And I run "boost list --tag fav"
+    Then the exit code should be 0
+    And the output should contain "brainstorming"
+    And the output should contain "#fav"
+
+  Scenario: --tag with no matching skills shows the tagged empty state
+    Given the "brainstorming" skill is installed
+    When I run "boost list --tag nope-tag"
+    Then the exit code should be 0
+    And the output should contain "no skills installed with tag #nope-tag"

boost_skill_cli-1.0.149/tests/bdd/features/mcp.feature

@@ -0,0 +1,31 @@
+Feature: boost mcp
+  Register boost as an MCP server for Claude Code. Never shells out to a real
+  `claude` CLI in these scenarios — shutil.which/subprocess.run are mocked.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: registering without the claude CLI prints the manual command
+    Given the "claude" CLI is not on PATH
+    When I run "boost mcp register"
+    Then the exit code should be 0
+    And the output should contain "`claude` CLI not found — run this yourself:"
+    And the output should contain "claude mcp add boost --scope user"
+
+  Scenario: registering with the claude CLI present succeeds
+    Given the "claude" CLI is on PATH and succeeds
+    When I run "boost mcp register"
+    Then the exit code should be 0
+    And the output should contain "registered boost as an MCP server (scope: user)"
+
+  Scenario: a claude mcp add failure surfaces the error
+    Given the "claude" CLI is on PATH but fails with "no auth"
+    When I run "boost mcp register"
+    Then the exit code should be 1
+    And the output should contain "claude mcp register failed: no auth"
+
+  Scenario: unregistering without the claude CLI prints the manual command
+    Given the "claude" CLI is not on PATH
+    When I run "boost mcp unregister"
+    Then the exit code should be 0
+    And the output should contain "claude mcp remove boost"

boost_skill_cli-1.0.149/tests/bdd/features/search.feature

@@ -0,0 +1,37 @@
+Feature: boost search
+  Search skills across tap registries, ranked by full-content BM25.
+
+  Background:
+    Given a fresh boost environment
+
+  Scenario: no taps configured fails with a hint
+    When I run "boost search anything"
+    Then the exit code should be 1
+    And the output should contain "no taps configured — nothing to search"
+    And the output should contain "boost tap --defaults"
+
+  Scenario: multi-word query ranks the exact match first
+    Given the fixture tap is added
+    When I run "boost search commit messages"
+    Then the exit code should be 0
+    And the output should contain "commit-messages"
+    And the output should contain "ranked by full-content BM25"
+
+  Scenario: no matches hints at discover
+    Given the fixture tap is added
+    When I run "boost search zzzznothing"
+    Then the exit code should be 0
+    And the output should contain "no matches for 'zzzznothing'"
+    And the output should contain "try `boost discover zzzznothing`"
+
+  Scenario: --json emits a single-line JSON document
+    Given the fixture tap is added
+    When I run "boost search brainstorming --json"
+    Then the exit code should be 0
+    And the output should match "\"name\": \"brainstorming\""
+
+  Scenario: --limit rejects a non-positive value
+    Given the fixture tap is added
+    When I run "boost search x --limit 0"
+    Then the exit code should be 2
+    And the output should contain "must be >= 1"