AGENT SKILL

bstack

Install or upgrade the bundled bstack collection when the user asks to set up or update bstack in a project.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
bstack
metadata
{ "package": "bstack" }
description
Install or upgrade the bundled bstack collection when the user asks to set up or update bstack in a project.

02 资源文件 270

03 SKILL.md 正文

Install bstack

This folder is the complete bstack 3.4.0 release. Keep its scripts, workflows, references, manifest, and license notices together. Bundled workflow bodies use INSTRUCTIONS.md, so only this installer appears before setup creates the project skills. It needs Python 3.11 or newer; no archive extraction or upstream download is required.

Target the Git repository containing the work. Resolve it with git rev-parse --show-toplevel, even if this installer lives elsewhere. Resolve scripts/bstack.py relative to this skill folder, choose an available Python 3.11+ interpreter, then run:

<python3.11-or-newer> <installed-bstack>/scripts/bstack.py install --project <project-root>

For a new installation, pass --hosts with the requested or available tools, including the current host: codex, claude, cursor, grok, amp, copilot, opencode. The default selects the first four. On upgrade, omit the flag to preserve the existing selection. New projects default to --auto on and --verification ask; upgrades preserve those settings unless explicitly changed.

Setup validates the complete manifest and selected interpreter before installing a private copy at .bstack/package/. It saves that interpreter for generated hooks. Keep the interpreter available; rerun setup with another supported interpreter to repair or change it. Respect ownership conflicts. Do not move or delete another installer's skills to force setup through. The installed package works after this distributor-owned folder is removed.

Run the installed controller's doctor with the same supported interpreter:

<python3.11-or-newer> <project-root>/.bstack/package/scripts/bstack.py doctor --project <project-root>

Doctor checks package integrity, owned bindings, and actual hook command startup. Native host loading, Codex trust, and delivery still need a fresh session in the target checkout. Follow the setup result's fresh_session_required and notice; a later status check does not clear that requirement. In Claude desktop, open a new Code chat rooted in the project. Installing in a parent repository does not configure a child repository.

Every developer runs setup in their own checkout. Commit portable AGENTS.md, CLAUDE.md, .gitignore, and a newly created PR template if desired. Generated skills, runtime state, and adapters belong to the checkout. The stable .bstack/ block and shared generated-path policy have separate ownership. Shared visibility exceptions survive setup, and uninstall preserves that policy. Review sharing for policy maintenance and visible or tracked generated paths; preserve unrelated configuration in mixed host settings.

Report auto, verification, pr_template, and any recovery_warning from setup. Existing PR templates stay unchanged; only replace a chosen template when requested. Codex's explicit hooks-off setting blocks automatic setup; the user can enable hooks or choose --auto off, which leaves its native guard unavailable. After successful doctor, suggest bstack-guide in the fresh session. Optional user-wide memory setup remains separate and requires its own request. Use the installed setup instructions for later configuration and optional setup.

04 同仓库更多 Skills

bbishdotdev
bbishdotdev/ai-tools

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

数据分析师
★ 0
bbishdotdev
bbishdotdev/ai-tools

unslop

Cut AI tells from any writing. Must always apply.

★ 0
bbishdotdev
bbishdotdev/ai-tools

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 0
bbishdotdev
bbishdotdev/ai-tools

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

开发工程师内容创作者写作与文案
★ 0
bbishdotdev
bbishdotdev/ai-tools

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

教师与教育
★ 0
bbishdotdev
bbishdotdev/ai-tools

tdd

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

★ 0