docbridge 0.4.0 → 0.4.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docbridge",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "A Bun CLI that links Markdown specifications and code declarations.",
   "license": "MIT",
   "type": "module",

package/templates/skills/README.md

@@ -1,10 +1,13 @@
 # DocBridge skill templates
 
-Distributable agent skills for projects that use DocBridge. Installation is
-copy-based: copy a skill directory into your repository's skill location
-(`.claude/skills/` for Claude Code or `.agents/skills/` for Codex-style
-project skills) and adjust nothing unless your DocBridge invocation differs
-from the examples inside.
+Distributable agent skills for projects that use DocBridge. Prefer
+`docbridge init` for CLI-driven setup or `docbridge init-with-agent` for
+agent-guided adoption. `init-with-agent` installs `docbridge-adopt` first;
+`docbridge-adopt` installs the companion skills after scope is confirmed.
+Manual copy-based installation remains available: copy a
+skill directory into your repository's skill location (`.claude/skills/` for
+Claude Code or `.agents/skills/` for Codex-style project skills) and adjust
+nothing unless your DocBridge invocation differs from the examples inside.
 
 - [`docbridge-annotate`](docbridge-annotate/SKILL.md) — create correct
   `@doc`/`@code` link pairs and verify them with `docbridge check`.
@@ -13,7 +16,8 @@ from the examples inside.
   then update the counterpart or justify leaving it unchanged.
 - [`docbridge-adopt`](docbridge-adopt/SKILL.md) — adopt DocBridge in an existing
   TypeScript, Swift, or Dart project by confirming docs/code scope, creating
-  or improving config, and handling simple CI/hook setup.
+  or improving config, installing companion skills, and handling simple CI/hook
+  setup.
 - [`docbridge-link`](docbridge-link/SKILL.md) — link existing docs sections to
   existing supported code declarations through docs-first candidate discovery
   and section-level confirmation.

package/templates/skills/docbridge-adopt/SKILL.md

@@ -6,8 +6,9 @@ description: Adopt DocBridge in an existing TypeScript, Swift, or Dart project.
 # docbridge-adopt
 
 Adopt DocBridge in an existing project. This skill assumes it is already
-installed in the agent environment; installing agent skills into another
-project is documented outside this skill.
+installed in the agent environment through `docbridge init-with-agent`,
+`docbridge init`, or a manual copy into `.agents/skills/` or
+`.claude/skills/`.
 
 The goal is to make the repository ready for DocBridge links, then continue
 into an initial docs-first link-candidate pass. Do not assume a pull request.
@@ -47,7 +48,24 @@ repo recipe such as `just check`, or
      improvement, and edit only after confirmation.
    - Never replace a user-authored config blindly.
 
-4. **Handle CI/hooks conservatively.**
+4. **Install companion DocBridge skills.**
+   - After scope is confirmed and `docbridge.config.json` exists or has been
+     intentionally left unchanged, install the rest of the distributable
+     DocBridge skills for the same agent target.
+   - Prefer the project-native DocBridge invocation. For example, run
+     `docbridge init --yes --agent-target codex`, `docbridge init --yes
+     --agent-target claude`, or `docbridge init --yes --agent-target both`
+     from the project root. Use the target that matches the existing
+     `.agents/` and/or `.claude/` setup.
+   - This command should leave an existing `docbridge.config.json` unchanged
+     and copy any missing `docbridge-annotate`, `docbridge-link`,
+     `docbridge-review`, and `docbridge-sync` skill directories. Do not use
+     `--force` unless the user explicitly asks to overwrite installed skills.
+   - If the command is unavailable, explain the blocker and provide the manual
+     copy target paths from `templates/skills/docbridge-*` instead of silently
+     skipping this step.
+
+5. **Handle CI/hooks conservatively.**
    - If the existing setup is simple and the user confirmed the mode, implement
      it.
    - If the setup is complex or ambiguous, provide a concrete patch plan or
@@ -55,11 +73,11 @@ repo recipe such as `just check`, or
    - Prefer non-blocking awareness early in adoption unless the user requests a
      hard gate.
 
-5. **Verify the setup.** Run `docbridge check` or the repository's equivalent.
+6. **Verify the setup.** Run `docbridge check` or the repository's equivalent.
    If the project intentionally has no links yet, a clean zero-link result is
    acceptable. Surface config or scanning diagnostics before proceeding.
 
-6. **Continue into initial candidate discovery.** After setup, inspect the
+7. **Continue into initial candidate discovery.** After setup, inspect the
    confirmed docs scope and present 5-10 high-value section candidates using
    the `docbridge-link` rules. Candidate discovery may continue in the same
    turn, but annotation edits still require section-level user confirmation.