← ClaudeAtlas

adoptlisted

Use when installing BrotherSBE into a repository that has not used it before, or when checking whether an existing installation is actually wired up. Inspects the repository for readiness, proposes a configuration, and reports what is present, what is missing and what it could not check. Dry run by default. Invoke as /brothersbe:adopt.
khalilmaaouni/BrotherSBE · ★ 0 · Data & Documents · score 68
Install: claude install-skill khalilmaaouni/BrotherSBE
# Adopt Dry run by default. This skill proposes and reports; it does not silently change a repository it was pointed at. Read `${CLAUDE_PLUGIN_ROOT}/SKILL.md` first, then `${CLAUDE_PLUGIN_ROOT}/docs/SETUP.md`. ## Run the proposal first Before inspecting anything by hand, run: ``` "${CLAUDE_PLUGIN_ROOT}/bin/sbe" adopt . ``` This is a dry run by default: it detects the stack and proposes the configuration without changing the repository. Read its output before doing anything else, it is the primary source the rest of this skill builds on. Reserve `--apply` for when the user explicitly asks to install the proposed configuration. ## What to inspect, in this order 1. **Stack**: languages present, test runner, migration tool, CI system, whether a data transformation layer exists. Detected from files, not asked. 2. **Wiring**: is the plugin installed and enabled; do the hooks resolve; is there a CI workflow that runs the gates on the merge path, or only beside it. 3. **Dossier**: does a design dossier exist, and does the tier it declares match the artifacts present. 4. **Protection**: can the workflow file, the hooks, or the policy be edited without review. This is the control everything else rests on: a gate that anyone can delete is a suggestion. ## Verify the installation mechanically ``` sh "${CLAUDE_PLUGIN_ROOT}/scripts/verify-install.sh" "${CLAUDE_PLUGIN_ROOT}/bin/sbe" fences . claude plugin validate "${CLAUDE_PLUGIN_ROOT}" ``` The middle command pr