[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MNFWDGJCKKGAZM3HQR3T5":3,"skill-same:01M71MNFWDGJCKKGAZM3HQR3T5":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M71MNFWDGJCKKGAZM3HQR3T5","install-bstack",null,"Install or upgrade the bundled bstack collection when the user asks to set up or update bstack in a project.","bbishdotdev\u002Fai-tools","bbishdotdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5323528?v=4","01M71MHYW2Q0DVZA22Q79M8KER","Brenden Bishop","01M71MHYWSMQWFPGA8CBJYQANH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Frelease\u002Fskills-sh\u002Finstall-bstack\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"install","install bstack","SET","upgrade","when","project","collection","update","user","up","2026-11-10 10:56:23",false,"---\nname: install-bstack\ndescription: Install or upgrade the bundled bstack collection when the user asks to set up or update bstack in a project.\nmetadata:\n  package: bstack\n---\n\n# Install bstack\n\nThis skill transports the reviewed bstack release. Its [archive](assets\u002Fbstack.zip) contains the package, dependencies, customizations, source manifest, and license notices. Do not fetch upstream skills or modify this distributor-owned archive.\n\nChoose an available Python 3.11+ interpreter; setup validates and saves its exact path for generated hooks. Rerun setup if that interpreter moves. Target the Git repository containing the work, even when this installer skill or another bstack package lives in a parent folder or the user's home directory. Resolve the active repository with `git rev-parse --show-toplevel`; use that path for `--project`. If the session starts above several repositories and the intended one is unclear, identify it before installing. Resolve [install.py](install.py) to its absolute path, then run:\n\n```sh\npython3.12 \u003Cinstalled-install-bstack>\u002Finstall.py --project \u003Cproject-root>\n```\n\nFor a new installation, select the requested hosts or detect available tools, including the current host, and pass `--hosts` with the relevant names: `codex`, `claude`, `cursor`, `grok`, `amp`, `copilot`, `opencode`. Without that flag, a new installation configures the first four; add the optional hosts explicitly when requested. For upgrades, omit `--hosts` to preserve the existing selection unless the user requests a change. Amp, Copilot, and OpenCode discover the shared skills and get native routing and PR-guard bindings: an Amp plugin, Copilot hook configuration, or an OpenCode plugin. Native folder trust and tool settings still apply. Verify Amp discovery with `amp skills list` in a fresh session, and check Copilot in its own client.\n\nThe installer validates and copies the package to `.bstack\u002Fpackage\u002F`, creates direct skill entries under `.agents\u002Fskills\u002F`, and connects the selected hosts. A new installation starts with automatic engineering routing on and project verification set to `ask`; upgrades preserve both choices. Auto routing picks relevant engineering workflows during ordinary prompts. Verification `ask` proposes changes to a project's verifier before editing it. The user can choose `--auto off` or `--verification off|ask|auto` during installation, or change either later with the installed controller. Respect ownership conflicts rather than overwriting them. The installed package is independent of this transport skill and the development checkout. Keep this skill intact so its distributor can update or remove it normally.\n\nIf Codex explicitly disables hooks, default setup stops. Explain the two simple options: enable hooks or install with `--auto off`. Do not silently change that host setting. Manual setup can complete, but the Codex PR guard cannot run until hooks are enabled.\n\nA package installed only in a parent directory is not setup for a child repository. Parent `CLAUDE.md` instructions may appear in Claude Code while the child's skills and auto hook are absent. Install into the child repository, run its `doctor`, then enable auto there if requested. In Claude Code desktop, start a Code chat rooted in that repository and open a fresh chat after setup. Do not report parent `doctor` success as proof for the child.\n\nSetup adds the seven-rule baseline inside managed blocks in `AGENTS.md` and, when Claude is selected, `CLAUDE.md`. It creates missing files, preserves surrounding project instructions, and follows existing links within the project without duplicating a shared block. The baseline applies with automatic routing off. Do not rewrite these blocks by hand or run a host's `\u002Finit` automatically.\n\nNew root instruction files are project files, not disposable installer state. Setup does not stage or commit them. Tell the user when they are untracked and suggest committing them if they want the guidance to survive a new checkout. On upgrade, if the result has `recreated_instruction_files`, report `recovery_warning` plainly: the installer rebuilt only its block and cannot recover missing project guidance outside it. An existing file with a changed or removed block still needs reconciliation; do not overwrite the whole file.\n\nAfter successful setup, offer to add project-specific guidance outside the blocks if needed. This is optional; installation is already complete. If the user requests it, inspect the repository and preserve the baseline. A host's native init is optional too, not a portable setup step. Run the installed `doctor` afterward. If an init removed or changed a block, preserve the new project guidance and restore the exact managed block from `.bstack\u002Fconfig.json` before rerunning setup; do not overwrite the whole file.\n\nThe entrypoint runs the installed package's `doctor` after installation. Report its `doctor` result and preserve the install result's `fresh_session_required` and `notice` guidance. A later status check does not clear that reload requirement. When required, tell Claude desktop users to start a new Code chat so it discovers the installed skills. Doctor also probes the exact generated commands without routing or writing verification receipts. A successful command check does not prove that a desktop app has discovered the skills or run its hooks.\n\nDoctor also lists optional model launchers and workflow readiness. A missing Codex, Claude Code, Cursor or Grok CLI does not spoil a basic installation. When the user chooses a model-backed workflow, run `doctor --live --workflow review-pr|grilling|to-pr` for that workflow. A broken selected role must be fixed before that workflow starts. If the developer uses a wrapper, ask for its working terminal command and configure it with `shared\u002Fmodel_cli.py configure --cli \u003Cname> --command 'wrapper {args}'`; rerun the live check. Do not guess a wrapper or silently switch providers. The `to-pr` probe tests Codex text access, not image generation.\n\nReport the install result's `pr_template` status. If setup created `.github\u002Fpull_request_template.md`, tell the user it is their editable project copy and should be committed to the default branch for GitHub to use it. If templates already existed, name every returned path, say setup left them unchanged, and point to `pr_template.bundled`. Offer: \"Want me to compare your current PR template with BStack's and replace the one you choose?\" If the user chooses to replace one, show the meaningful differences, save its current contents, and change only the file they selected. A multi-template directory needs a specific file choice; do not add a competing default template silently. Do not ask again when the user already requested that exact replacement.\n\nUse a supported in-session refresh capability only if the host actually exposes one, and verify its result. Otherwise give the fresh-session instruction; do not simulate a refresh by running a separate CLI process or resetting the user's chat. Claude's `\u002Freload-skills`, where available, refreshes the skill catalog only; it does not replace a required session change for routing instructions or hooks.\n\nAfter `doctor` succeeds, report its `auto` and `verification` settings plainly. If auto is off, explain that engineering routing is manual and that `$bstack-auto on` in Codex or `\u002Fbstack-auto on` in slash-command hosts enables it. Do not override an existing off preference. For project verifier behavior, the installed controller accepts `verification off|ask|auto`; explain a choice only if the user asks to change it. Installation or `doctor` failures come first.\n\nAfter a successful `doctor`, point the user to `bstack-guide` for a short walkthrough and help choosing a first workflow. If they asked to learn bstack during installation, read the installed `.bstack\u002Fpackage\u002Fshared\u002Fbstack-guide\u002FINSTRUCTIONS.md` and give that walkthrough now. Otherwise recommend `$bstack-guide` in Codex or `\u002Fbstack-guide` in slash-command hosts. When a fresh session is required, say to invoke it in that new session; do not imply this chat's skill catalog has reloaded.\n\nShared memory is bundled but inactive. If the user also requests it, use the installed `setup-bstack` skill's optional memory setup. Do not change user-wide memory settings as part of ordinary project installation.\n\nThe PR creation guard is installed for every selected host even with auto routing off. It redirects raw PR creation and body replacement to `to-pr`. Binding checks do not prove a native denial; consult the recorded compatibility limits. Codex users still need to review hook trust in the terminal CLI; setup never grants it. If Codex hooks are explicitly disabled, a manual install can complete but the guard cannot run there. Automatic Codex routing requires hooks to be enabled.\n","# Install bstack\n\nThis skill transports the reviewed bstack release. Its [archive](assets\u002Fbstack.zip) contains the package, dependencies, customizations, source manifest, and license notices. Do not fetch upstream skills or modify this distributor-owned archive.\n\nChoose an available Python 3.11+ interpreter; setup validates and saves its exact path for generated hooks. Rerun setup if that interpreter moves. Target the Git repository containing the work, even when this installer skill or another bstack package lives in a parent folder or the user's home directory. Resolve the active repository with `git rev-parse --show-toplevel`; use that path for `--project`. If the session starts above several repositories and the intended one is unclear, identify it before installing. Resolve [install.py](install.py) to its absolute path, then run:\n\n```sh\npython3.12 \u003Cinstalled-install-bstack>\u002Finstall.py --project \u003Cproject-root>\n```\n\nFor a new installation, select the requested hosts or detect available tools, including the current host, and pass `--hosts` with the relevant names: `codex`, `claude`, `cursor`, `grok`, `amp`, `copilot`, `opencode`. Without that flag, a new installation configures the first four; add the optional hosts explicitly when requested. For upgrades, omit `--hosts` to preserve the existing selection unless the user requests a change. Amp, Copilot, and OpenCode discover the shared skills and get native routing and PR-guard bindings: an Amp plugin, Copilot hook configuration, or an OpenCode plugin. Native folder trust and tool settings still apply. Verify Amp discovery with `amp skills list` in a fresh session, and check Copilot in its own client.\n\nThe installer validates and copies the package to `.bstack\u002Fpackage\u002F`, creates direct skill entries under `.agents\u002Fskills\u002F`, and connects the selected hosts. A new installation starts with automatic engineering routing on and project verification set to `ask`; upgrades preserve both choices. Auto routing picks relevant engineering workflows during ordinary prompts. Verification `ask` proposes changes to a project's verifier before editing it. The user can choose `--auto off` or `--verification off|ask|auto` during installation, or change either later with the installed controller. Respect ownership conflicts rather than overwriting them. The installed package is independent of this transport skill and the development checkout. Keep this skill intact so its distributor can update or remove it normally.\n\nIf Codex explicitly disables hooks, default setup stops. Explain the two simple options: enable hooks or install with `--auto off`. Do not silently change that host setting. Manual setup can complete, but the Codex PR guard cannot run until hooks are enabled.\n\nA package installed only in a parent directory is not setup for a child repository. Parent `CLAUDE.md` instructions may appear in Claude Code while the child's skills and auto hook are absent. Install into the child repository, run its `doctor`, then enable auto there if requested. In Claude Code desktop, start a Code chat rooted in that repository and open a fresh chat after setup. Do not report parent `doctor` success as proof for the child.\n\nSetup adds the seven-rule baseline inside managed blocks in `AGENTS.md` and, when Claude is selected, `CLAUDE.md`. It creates missing files, preserves surrounding project instructions, and follows existing links within the project without duplicating a shared block. The baseline applies with automatic routing off. Do not rewrite these blocks by hand or run a host's `\u002Finit` automatically.\n\nNew root instruction files are project files, not disposable installer state. Setup does not stage or commit them. Tell the user when they are untracked and suggest committing them if they want the guidance to survive a new checkout. On upgrade, if the result has `recreated_instruction_files`, report `recovery_warning` plainly: the installer rebuilt only its block and cannot recover missing project guidance outside it. An existing file with a changed or removed block still needs reconciliation; do not overwrite the whole file.\n\nAfter successful setup, offer to add project-specific guidance outside the blocks if needed. This is optional; installation is already complete. If the user requests it, inspect the repository and preserve the baseline. A host's native init is optional too, not a portable setup step. Run the installed `doctor` afterward. If an init removed or changed a block, preserve the new project guidance and restore the exact managed block from `.bstack\u002Fconfig.json` before rerunning setup; do not overwrite the whole file.\n\nThe entrypoint runs the installed package's `doctor` after installation. Report its `doctor` result and preserve the install result's `fresh_session_required` and `notice` guidance. A later status check does not clear that reload requirement. When required, tell Claude desktop users to start a new Code chat so it discovers the installed skills. Doctor also probes the exact generated commands without routing or writing verification receipts. A successful command check does not prove that a desktop app has discovered the skills or run its hooks.\n\nDoctor also lists optional model launchers and workflow readiness. A missing Codex, Claude Code, Cursor or Grok CLI does not spoil a basic installation. When the user chooses a model-backed workflow, run `doctor --live --workflow review-pr|grilling|to-pr` for that workflow. A broken selected role must be fixed before that workflow starts. If the developer uses a wrapper, ask for its working terminal command and configure it with `shared\u002Fmodel_cli.py configure --cli \u003Cname> --command 'wrapper {args}'`; rerun the live check. Do not guess a wrapper or silently switch providers. The `to-pr` probe tests Codex text access, not image generation.\n\nReport the install result's `pr_template` status. If setup created `.github\u002Fpull_request_template.md`, tell the user it is their editable project copy and should be committed to the default branch for GitHub to use it. If templates already existed, name every returned path, say setup left them unchanged, and point to `pr_template.bundled`. Offer: \"Want me to compare your current PR template with BStack's and replace the one you choose?\" If the user chooses to replace one, show the meaningful differences, save its current contents, and change only the file they selected. A multi-template directory needs a specific file choice; do not add a competing default template silently. Do not ask again when the user already requested that exact replacement.\n\nUse a supported in-session refresh capability only if the host actually exposes one, and verify its result. Otherwise give the fresh-session instruction; do not simulate a refresh by running a separate CLI process or resetting the user's chat. Claude's `\u002Freload-skills`, where available, refreshes the skill catalog only; it does not replace a required session change for routing instructions or hooks.\n\nAfter `doctor` succeeds, report its `auto` and `verification` settings plainly. If auto is off, explain that engineering routing is manual and that `$bstack-auto on` in Codex or `\u002Fbstack-auto on` in slash-command hosts enables it. Do not override an existing off preference. For project verifier behavior, the installed controller accepts `verification off|ask|auto`; explain a choice only if the user asks to change it. Installation or `doctor` failures come first.\n\nAfter a successful `doctor`, point the user to `bstack-guide` for a short walkthrough and help choosing a first workflow. If they asked to learn bstack during installation, read the installed `.bstack\u002Fpackage\u002Fshared\u002Fbstack-guide\u002FINSTRUCTIONS.md` and give that walkthrough now. Otherwise recommend `$bstack-guide` in Codex or `\u002Fbstack-guide` in slash-command hosts. When a fresh session is required, say to invoke it in that new session; do not imply this chat's skill catalog has reloaded.\n\nShared memory is bundled but inactive. If the user also requests it, use the installed `setup-bstack` skill's optional memory setup. Do not change user-wide memory settings as part of ordinary project installation.\n\nThe PR creation guard is installed for every selected host even with auto routing off. It redirects raw PR creation and body replacement to `to-pr`. Binding checks do not prove a native denial; consult the recorded compatibility limits. Codex users still need to review hook trust in the terminal CLI; setup never grants it. If Codex hooks are explicitly disabled, a manual install can complete but the guard cannot run there. Automatic Codex routing requires hooks to be enabled.\n",{"name":5,"metadata":34,"description":7},{"package":35},"bstack","main","10ff9ff4e26809063b10c95ac2357302d0d34543","bstack\u002Frelease\u002Fskills-sh\u002Finstall-bstack","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools","https:\u002F\u002Fgithub.com\u002Fbbishdotdev","bbish.dev","Husband | Father | Technologist\r\nEngineering leader helping product and delivery teams use AI to build better systems, habits, and tools.","2026-11-11 11:13:39",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add bbishdotdev\u002Fai-tools --skill install-bstack",{"tool":50,"command":51},"bunx","bunx skills add bbishdotdev\u002Fai-tools --skill install-bstack",{"tool":53,"command":54},"pnpm","pnpm dlx skills add bbishdotdev\u002Fai-tools --skill install-bstack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Frelease\u002Fskills-sh\u002Finstall-bstack\u002FSKILL.md",true,[58,64,70,76],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"agents\u002Fopenai.yaml","REFERENCE","参考文档",42,"https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Frelease\u002Fskills-sh\u002Finstall-bstack\u002Fagents\u002Fopenai.yaml",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"assets\u002Fbstack.zip","ASSET","资产文件",738115,"https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Frelease\u002Fskills-sh\u002Finstall-bstack\u002Fassets\u002Fbstack.zip",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"install.py","SCRIPT","脚本",2586,"https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Frelease\u002Fskills-sh\u002Finstall-bstack\u002Finstall.py",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Finstall.py",5631,"https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Frelease\u002Fskills-sh\u002Finstall-bstack\u002Fscripts\u002Finstall.py",[81,112,124,139,172,195],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":29},"01M71MT5NBY3RY660EA06K9CA1","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.","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Fupstream\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[83,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"how","parallel","observability","warehouse","returns","infrastructure","source","analytics","data","issue","read","tracker","product","work","design","product analytics","time","error tracking","error",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":29},"01M71MT4CFF7AK4TRV40P7ZZ30","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Fupstream\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[114,119,120,121,122,123],"cut","true","ai tells","apply","writing",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":29},"01M71MT37W015EGE0EB82JQYAM","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Fupstream\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[131,132,133,134,135,23,136,137,120,138],"typescript","typescript best practices","best practices","use","tsx","editing","file","reading",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":156,"publishedAt":29},"01M71MT1092N34HQMGECW170JP","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Fupstream\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[145,150,153],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":151,"categoryName":152,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":154,"categoryName":155,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000036","内容创作者",[157,123,158,159,160,161,162,163,164,165,23,166,167,134,120,168,141,169,170,171],"technical","technical writing","commit messages","google","syntax","style","structure","layered","english","commit","Rules","messages","for","pr","standard",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":29},"01M71MSYRMT7KZPQFY7A2ZHGMB","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'.","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Fupstream\u002Fpstack\u002Fskills\u002Fteach\u002FSKILL.md",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000039","教师与教育",[174,169,93,182,183,184,106,185,186,187,188,189,134,190,191,120,192,193,83,194],"me","explanation","change","help","one","it","explain","body","teach me","understand","clear","person","find",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":29},"01M71MSWTVAEVMZAG7SMWFE1FE","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.","https:\u002F\u002Fgithub.com\u002Fbbishdotdev\u002Fai-tools\u002Fblob\u002Fmain\u002Fbstack\u002Fupstream\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[197,134,202,27,203,23,204,120,205,206,207,208,209,169,210,211],"path","regression test","only","local","failing","bug","integration","regression","target","test"]