Add Claude Code Plugin setup page

[samgutentag]

Summary

• Adds a new docs page for the Claude Code Plugin setup alongside the existing MCP server (CLI) setup page
• Covers plugin install via the community plugins directory, OAuth authentication, slash commands (fix-flaky, why-flaky, setup-uploads), and auto-activating skills
• Manual GitHub URL install included as a fallback behind a details dropdown
• Wires the page into summary.md navigation and the configuration card grid

Test plan

• Verify /plugin install trunk@claude-plugin-directory resolves from the community directory
• Verify /plugin install trunk@https://github.com/trunk-io/claude-code-plugin works as fallback
• Verify GitBook preview renders the new page correctly (including details dropdown)
• Confirm the card grid on the Configuration page links to the new page
• Confirm navigation sidebar shows "Claude Code Plugin" after "Claude Code (CLI)"
• Review content accuracy against the plugin repo

Generated with Claude Code

[trunk-staging-io]

😎 Merged successfully - details.

[claude]

Claude finished @samgutentag's task in 1m 18s —— View job

---

PR Review

• Gather context and read changed files
• Review for typos, grammar, and formatting
• Review documentation best practices
• Post inline comments for specific issues
• Summarize findings

---

Summary

The new claude-code-plugin.md page is well-structured and the navigation wiring (summary.md, README.md) looks correct. However, there is one blocking issue and a few minor style nits.

Blocking

• Line 12 — The primary install command /plugin install trunk@claude-plugin-directory is broken until the plugin lands in the official Anthropic directory (explicitly called out as a blocker in the PR description). The page should either lead with the working direct-URL install (/plugin install trunk@https://github.com/trunk-io/claude-code-plugin) or add a clear caveat, before this page ships.

Non-blocking

• Line 17 — "run /plugin from Claude Code" is vague; the exact command isn't spelled out.
• Line 42 — "Say yes" is informal; "Confirm to apply" is more consistent with the rest of the doc's tone.
• Line 58 — "copy-pasteable" is informal; "ready-to-paste" reads better in docs.

Inline suggestions posted for all four items above.

[claude]

Claude finished @samgutentag's task in 1m 19s —— View job

---

PR Review

• Gather context and read changed files
• Review for typos, grammar, and formatting
• Review documentation best practices
• Post inline comments for specific issues
• Summarize findings

---

Summary

The structure, navigation wiring (summary.md, README.md), and overall content of claude-code-plugin.md are solid. The previous feedback on "copy-pasteable" and the vague auth instruction have been addressed. Three issues remain:

Blocking

• Line 14 — The primary install command /plugin install trunk@claude-plugin-directory still won't resolve until the plugin is listed in the official Anthropic directory — the stated reason this PR is on hold. The <details> alternative (GitHub URL) is the only working install path right now. Consider swapping them: lead with the direct-URL install, and put the directory install in <details> as "once approved". Fix this →

Non-blocking

• Line 17 — The link points to anthropics/claude-plugins-community but the PR description references anthropics/claude-plugins-official as the relevant directory. Please verify which repo is correct and align the link.
• Line 56 — "Say yes" remains informal compared to the rest of the doc's tone; suggest "Confirm to apply the changes directly."

[samgutentag]

Triage status (2026-05-05): merge conflicts with main in summary.md and flaky-tests/use-mcp-server/configuration/README.md. Branch is 9 commits ahead with your iterations. Just needs final conflict resolution.

[samgutentag]

Verification status (2026-05-07, re-verified): unknown

Could not determine state from feature-rollout signals (no eng PR or Linear ticket to verify against), but verifying directly against the external systems:

• Plugin repo exists: trunk-io/claude-code-plugin is public.
• Plugin is live in the community marketplace: confirmed by reading .claude-plugin/marketplace.json directly from anthropics/claude-plugins-community. The marketplace declares its name as claude-community and lists trunk with source URL https://github.com/trunk-io/claude-code-plugin.git and homepage https://docs.trunk.io/flaky-tests/use-mcp-server. The primary install command on line 20 (claude plugin install trunk@claude-community) resolves correctly.
• Earlier review nits all addressed: line 62 uses "Confirm to apply" (replacing "Say yes"); line 78 uses "ready-to-paste" (replacing "copy-pasteable"); install commands now use the two-step marketplace flow.
• Stale wording fixed in follow-up commit 44bda68: line 35 in the details block previously said "before they land in the community directory" (written when the plugin wasn't listed yet). Now reads "before publishing a new release."

Note on earlier verification miss: the prior version of this comment said the plugin was not in the directory. That was a code-search false negative. The marketplace.json has 1920 plugins and substring search across the repo doesn't index it well. Verifying via marketplace.json directly is the right check.

Merge readiness:

• 2026-05-05 triage flagged conflicts in summary.md and flaky-tests/use-mcp-server/configuration/README.md. Local worktree is up to date with origin and not yet rebased. Conflict resolution still required before merge.
• Optional consistency pass: line 14 and line 20 use shell-style commands (claude plugin marketplace add, claude plugin install); line 32 uses slash-style (/plugin install). Both are valid in their respective contexts but worth aligning to one convention.

Suggested next action: rebase against current main, resolve the two conflicts, then merge. No remaining content blockers.

[claude]

Claude finished @samgutentag's task in 1m 46s —— View job

---

PR Review

• Read changed files
• Review for typos, grammar, and formatting
• Review documentation best practices
• Post inline comments for specific issues
• Summarize findings

---

Summary

The page is in good shape. Sam's 2026-05-07 verification confirms the plugin is live in the community marketplace, all earlier review nits ("Say yes" → "Confirm to apply", "copy-pasteable" → "ready-to-paste", stale "before they land in the directory" wording, vague auth instructions) have been addressed, and the merge into main has resolved the previously-flagged conflicts in summary.md and configuration/README.md. No remaining content blockers.

Non-blocking nits (inline comments posted):

• Lines 13, 19, 31, 58, 66, 74 — Code blocks are bare ``` while the sibling claude-code-cli.md tags shell blocks as ```bash. Worth aligning for syntax highlighting and consistency.
• Lines 14/20 vs 32 — Shell-style (claude plugin install …) and slash-style (/plugin install …) are mixed. Both are correct for their contexts (terminal vs. inside Claude Code), but a one-line lead-in or aligning to a single form would prevent confusion. Sam himself flagged this in the 2026-05-07 triage.
• Line 46 — Missing terminal period at the end of step 4 in the auth list.

No blockers — review_passed.
• Branch

[claude]

Code blocks on this page (lines 13, 19, 31, 58, 66, 74) are unfenced (bare ), but the sibling claude-code-cli.md page uses ```bash for shell commands. For consistency and syntax highlighting in GitBook, consider tagging the language on each block.

Suggested change

	```
	claude plugin marketplace add anthropics/claude-plugins-community
	```
	```bash
	claude plugin marketplace add anthropics/claude-plugins-community

[claude]

Command syntax is mixed across the page: lines 14 and 20 use shell-style (claude plugin marketplace add …, claude plugin install …), while line 32 uses slash-style (/plugin install …). Both are valid in their respective contexts (terminal vs. inside Claude Code), but the inconsistency may confuse readers.

Consider either (a) aligning to the same form as the primary install (shell-style):

Suggested change

	```
	/plugin install trunk@https://github.com/trunk-io/claude-code-plugin
	```
	```bash
	claude plugin install trunk@https://github.com/trunk-io/claude-code-plugin

…or (b) keeping the slash-style and adding a short clarifying lead-in such as "From inside Claude Code, run:" so the context shift is explicit.

[claude]

Missing terminal period after "terminal" — this sentence is the only one in the numbered list without a closing period.

Suggested change

	4. You'll see `Authentication successful. Connected to trunk.` back in the terminal
	4. You'll see `Authentication successful. Connected to trunk.` back in the terminal.

[github-actions]

Auto-approved: Claude code review passed.