bond

Dev workflow commands and MCP integrations for Claude Code. Built inside Bonliva, but every command resolves a per-repo profile, so they work outside it too.

Commands

Every command except /help opens with one question carrying each decision its arguments leave open — target, scope, and every push, PR, merge or tracker write it will make — and none when the arguments settle it all; after the answer it runs to the end. The rule is Commands ask first in shared/standing-rules.md, and tests/commands-ask-first.test.mjs fails a command that lacks the step.

Command	Purpose
`/help`	List all bond plugin commands with their descriptions
`/checkpoint`	Save, compare against, list or restore named snapshots of the working tree without committing
`/chrome-debug`	Fallback browser path: set up/open a debuggable Chrome (LaunchAgent) + install the chrome-devtools MCP pointed at it, when claude-in-chrome can't be used
`/fix-ci`	Fix a failed pipeline from its URL (Woodpecker, GitHub Actions, Bitbucket), a PR, or `--mine`: diagnose, fix, push, watch the re-run
`/disk-analyze`	Analyze disk usage: runaway logs, deleted-but-open files, caches; clean the safe ones
`/implement-batch`	Implement many tickets (Jira version/epic/JQL, GitHub milestone) in parallel worktrees, scheduled so no two touch the same files
`/implement`	Fetch (or create) a Jira ticket — or take a free-text task where there is no tracker — then branch, plan, and code
`/investigate`	Investigate a deployed failure to a proven root cause and write the investigation doc
`/linkedin`	Write a LinkedIn post or article from the source, facts and numbers checked, with an optional cover-image prompt
`/linkedin-draft`	Put an approved post or article into LinkedIn's composer or article editor through Chrome — a draft, never published
`/jira`	Create, edit, assign, comment on, or transition a Jira issue (assigned to you by default)
`/open-pr`	Open a PR for the current branch (GitHub or Bitbucket; draft in Bonliva repos)
`/sweep-pr`	Sweep open PRs: retarget the base, rebase, restart infra CI once, squash-merge the green ones under `--merge`, clean up
`/rebase`	Rebase (or merge, for a shared branch) onto the base, resolve conflicts, re-test, push with `--force-with-lease`
`/ship-pr`	After implement/fix-qa: browser-test the PR, tick its test plan, mark ready, loop review → fix → CI
`/worktree`	`open` a worktree for a branch, ticket or PR (env files + deps), `close` it, `prune` merged and stale ones
`/start`	Check out a fresh typed branch — creating the Jira issue first where there is a tracker

bond-bonliva (Bonliva-only companion)

plugins/bond-bonliva/ is a second plugin in the same marketplace. It depends on bond and carries everything that only makes sense inside Bonliva: the MCP server template and its setup, time logging, Teams and Bitbucket reviewer defaults. Enable it per Bonliva repo, not globally, so personal repos never load its commands or MCP tool listings:

// <bonliva repo>/.claude/settings.local.json
{ "enabledPlugins": { "bond-bonliva@devmaxxx": true } }

Command	Purpose
`/bond-bonliva:fix-qa`	Re-run implementation against QA feedback — from a Jira ticket, or free text
`/bond-bonliva:jira-sync`	Move tickets of merged PRs to QA (with fixVersion) and open PRs to In Review; `--qa-plan` posts manual test plans
`/bond-bonliva:log-plan`	Generate a day/week/month time-log plan
`/bond-bonliva:projects`	Manage the projects tracked by `log-plan` (add, remove, discover, clear)
`/bond-bonliva:publish-timelog`	Publish a time-log md to Jira + Clockify (one entry/day) and reconcile totals
`/bond-bonliva:publish-doc`	Publish a markdown doc to Outline, keeping its id and hash in frontmatter to catch remote edits
`/bond-bonliva:request-review`	Post a Teams card inviting reviewers to review a PR
`/bond-bonliva:set-reviewers`	Set or change the default reviewers added to PRs
`/bond-bonliva:setup-plugin`	Install the Bonliva MCP servers (local scope, per project) and env vars
`/bond-bonliva:teams-post`	Post a message to a Teams channel via a Workflow webhook

Skills (plugins/bond-bonliva/skills/):

port-from-prototype — diff a bonliva-prototypes screen against the app page (components, columns, fonts, colours, states), then port it with ui-kit components and existing tokens only.
crashlytics-triage — a Crashlytics issue URL or ios|android <version>, last N days: find our frame, sort real / upstream / noise, file BON bugs after showing the list, optionally a fix PR on release/*.
rn-mobile-build — Expo / React Native chores for the mobile app: cache cleaning, fastlane and ios:beta failures, simulator and emulator login, library upgrades, git-flow release finish.
mongo-migration — idempotent, batched bulkWrite migrations with a 10-document dry run, a verification query and Atlas index notes for the release.

Hook: PreToolUse on Write / Edit / MultiEdit runs plugins/bond-bonliva/hooks/migration-guard.mjs — a new file under a migrations/ directory is blocked while this branch already adds an unmerged migration the base does not have (update that one instead), or when its name is not kebab-case with a timestamp prefix that sorts after everything there and in the base (prefix width taken from the files already there). BOND_MIGRATION_GUARD=off turns it off. Unit-tested in tests/migration-guard.test.mjs.

Shared docs it reads (project-profile.md, implement-flow.md, jira.md) are symlinks into bond, which the plugin cache resolves into real copies.

bond-cockpit (job, prompt-cache status line and pane)

plugins/bond-cockpit/ is a mod: a plugin of function hooks (hooks/hooks.json → modules) that runs inside Claude Code rather than as spawned node processes, so it needs a build with plugin hook modules. It is opt-in and depends on bond:

// ~/.claude/settings.json
{ "enabledPlugins": { "bond-cockpit@devmaxxx": true } }

Status line — cache <hit>% ⏱<left> for the last main-thread request.
Pane — docks to the right of the transcript in the fullscreen layout from 110 columns (opened unasked, from 144), inline above the prompt otherwise. Three tabs, main first and in front (ctrl+x tab cycles them; /bond-cockpit job or session opens one). main keeps only what matters now: the task, then a few lines from each other tab under a heading that opens it (press it, or j / s in the pane) — under job, what runs now and agents working with a workflow's finished/started count; under session, the cache hit and countdown, the main model with its own tokens and requests, and the 5h and context gauges (other limits only once they turn yellow or red). job has the full Job card, then the Cache card. session has the Session card. The Job card: the prompt being worked on, its elapsed time (took … once done), what runs now — the tool in flight with what it works on and for how long, approve? when the permission check asked, thinking, or waiting for you — the tool count with failures and the last tool, a workflow gauge of the run's finished over started agents with the script's name and run id, and two lines per agent loop (subagent, teammate or workflow agent): its name and model from the spawn, calls and run time, then its latest tool and last test, typecheck or lint counts — red when any failed, with a warning when it ran git push or gh pr create. Working ones first, quiet after two minutes without a call, gone five minutes after finishing. The main tab's agents row adds the red and pushed counts. Press an agent's name (ctrl+x into the pane, arrows, Enter) and an agent tab opens: its state, run, model, its last 12 calls with their ages, and a message line that sends it a note the way SendMessage does — to check on it or change what it does next. The Cache card wears the entry's state on its border and header (● warm, ◐ expiring, ○ expired): the hit rate beside one bar split into read / wrote / new tokens, then a TTL meter with the countdown, and advice only once there is something to do. Session stays grey: hit rate with a sparkline of the last 20 requests coloured by hit, cost relative to no cache with the input tokens saved after the write surcharge, and prefix rebuilds (requests under 50% hit) with how long ago the last one was; then a models section, every model that answered this session, subagents included, with its requests and tokens and the main thread's marked; then a usage section of aligned gauges for the 5h and weekly rate-limit windows with time to reset and for the context fill, coloured at 75% and 90%. Its badge adds the session's cost. Bars stretch to the pane's width. /bond-cockpit opens it.
Cache toast — cache expires in 10s: send a message now, once per cache entry and never mid-turn, so a reply sent in time is read from cache instead of written again.

No request reports its cache TTL, so cacheTtl (default auto) infers it on every request: a subscription past a rate-limit window is in overage and drops to 5m; otherwise the last model switch's report; otherwise 1h on a subscription and 5m on an API key. 5m or 1h fixes it. The card badge says overage, set or API when the TTL came from one of those. cacheWarnSeconds (default 10, 0 off) sets when the toast fires.

bond-beauty-crm (beauty-crm-only companion)

plugins/bond-beauty-crm/ drives beauty-crm's own task flow (pnpm tasks), which bond's Jira/gh commands do not know. Enable it in the beauty-crm clone only:

// beauty-crm/.claude/settings.local.json
{ "enabledPlugins": { "bond-beauty-crm@devmaxxx": true } }

Command	Purpose
`/bond-beauty-crm:batch`	Close several milestone tasks that share files in one PR: `claim`, `claim --join`, `done` each, one `pr`
`/bond-beauty-crm:implement`	Start a task: claim its card, ask every question before the first edit (`shared/questions-first.md`), build, `done`, `pr`

bond-oss (open-source library companion)

plugins/bond-oss/ creates, audits, demos and releases npm libraries on one stack (pnpm, tsdown, Vitest, @antfu/eslint-config, ESM-only) and publishes them through npm trusted publishing (OIDC, no token). Its skills — oss-lib-stack, npm-publishing, oss-release-flow, oss-demos — carry the traps the libraries already hit; templates/ holds the files a new lib starts from. Personal names (GitHub owner, license holder, npm user) live in ~/.config/bond/oss.json, never in the plugin.

// ~/.claude/settings.json (or a library's .claude/settings.local.json)
{ "enabledPlugins": { "bond-oss@devmaxxx": true } }

Command	Purpose
`/bond-oss:new-lib`	Free-name check, scaffold from `templates/ts-lib`, GitHub repo, CI + release workflows, README, examples, first PR
`/bond-oss:audit`	Check a lib against the stack and its alternatives; fix license, package, CI, README and examples drift in one PR
`/bond-oss:demo`	Examples run in CI, a GitHub Pages or Expo demo, GIFs recorded by committed scripts
`/bond-oss:release`	Milestone, release PR, merge on green, tag, one watched run, npm + GitHub release verified; bootstraps trusted publishing on a first release

MCP Servers

bond-bonliva ships an MCP server template in plugins/bond-bonliva/.mcp.json. Run /bond-bonliva:setup-plugin to install those servers into the local scope of each Bonliva project, so they load only there. To avoid colliding with any servers you already run, each is installed under a bond- prefixed name and exposed as mcp__bond-<name>__*:

bond-atlassian — official Atlassian remote MCP server (https://mcp.atlassian.com/v1/mcp, OAuth, no env vars). Opens a browser on first use.
bond-bitbucket — bitbucket-mcp-py (PRs, repositories, pipelines)
bond-clockify — mcp_clockify (time entries, projects, tasks, workspaces)
bond-teams — @floriscornel/teams-mcp (Microsoft Teams chats, channels, messages). No env vars; auth is a one-time CLI step (see below).
bond-outline — outline-mcp-server (Outline docs, collections, search)

/bond-bonliva:setup-plugin prompts for any missing credentials and writes them via the claude mcp CLI. You can also export them in your environment beforehand so the command picks them up without prompting:

export BITBUCKET_USERNAME="you@bonliva.dev"
export BITBUCKET_TOKEN="…"
export CLOCKIFY_API_KEY="…"
export OUTLINE_API_KEY="…"
export OUTLINE_API_URL="https://docs.bonliva.dev/api"

BITBUCKET_WORKSPACE defaults to https://bitbucket.org — override if needed. OUTLINE_API_URL has no default — /bond-bonliva:setup-plugin prompts for it. Use https://docs.bonliva.dev/api for the Bonliva instance, or https://app.getoutline.com/api for Outline cloud.

bond-teams has no env vars. After /bond-bonliva:setup-plugin, authenticate it once with a Microsoft Graph OAuth flow:

npx -y @floriscornel/teams-mcp@latest authenticate

Teams channel webhook

bond-teams needs a Microsoft Graph token, which a tenant Conditional Access policy can block (e.g. device-compliance requirements). For one-way posting to a Teams channel, the /bond-bonliva:teams-post command sidesteps Graph entirely: it POSTs to a Power Automate Workflow webhook, whose URL is a bearer secret with no OAuth.

This posts to a channel only — not to 1:1 or group chats.

Create the webhook once, in the Teams client:

Open the target channel → ⋯ → Workflows.
Choose the template "Post to a channel when a webhook request is received."
Finish the wizard and copy the generated HTTP POST URL.

Then make the URL available as BOND_TEAMS_WEBHOOK_URL (treat it as a secret). Either let /bond-bonliva:setup-plugin prompt for it and store it in ~/.claude/settings.json (env block), or export it yourself:

export BOND_TEAMS_WEBHOOK_URL="https://…"

Now /bond-bonliva:teams-post <message> delivers a card to that channel. The underlying plugins/bond-bonliva/scripts/teams-post.sh is also usable standalone (CI, hooks):

BOND_TEAMS_WEBHOOK_URL="https://…" plugins/bond-bonliva/scripts/teams-post.sh --title "Deploy" "Build #42 passed"

Browser access

Anything in this plugin that needs a browser — reading a Jira attachment, pulling Teams calls in /log-plan, opening a failing page in /investigate — uses claude-in-chrome whenever it is available. It drives the user's real Chrome through the browser extension, so the SSO sessions are already there and no profile, LaunchAgent or debug port has to be stood up first. Load the tools with ToolSearch (select:mcp__claude-in-chrome__tabs_context_mcp,…) before using them.

Fall back to /chrome-debug and the CDP-based chrome-devtools MCP only when claude-in-chrome cannot do the job:

the extension is not installed, or has not been granted the site
the task needs raw CDP — a performance trace, a heap snapshot, a Lighthouse audit, evaluate_script against a target
it has to run unattended: CI, a hook, headless

If neither is available, skip the step and say so rather than asking the user to sign in — never enter credentials on their behalf.

Chrome debug (fallback, for the chrome-devtools MCP)

/chrome-debug lets Claude drive a real, logged-in browser instead of the chrome-devtools MCP's throwaway one. It installs a per-user macOS LaunchAgent that keeps a debuggable Chrome alive, and installs/points the MCP at it.

/chrome-debug            # setup: LaunchAgent + start + install bond-chrome-devtools MCP
/chrome-debug open https://localhost:8000   # ensure running, open a URL, focus
/chrome-debug status     # plist state, port reachability, Chrome version
/chrome-debug stop       # unload the agent

Why a dedicated profile: Chrome 136+ refuses --remote-debugging-port on the default profile, so the agent runs Chrome with a separate --user-data-dir (~/.chrome-debug). Your everyday Chrome is untouched and runs alongside it. The SSO session persists in that profile, so you only sign in once.

It installs a user-scope MCP server bond-chrome-devtools that runs npx chrome-devtools-mcp@latest --browserUrl=http://127.0.0.1:9222, attaching to the debug Chrome rather than launching its own. After setup, reconnect it (/mcp → bond-chrome-devtools → Reconnect) or restart Claude Code.

The underlying scripts/chrome-debug.sh is usable standalone (CI, hooks):

scripts/chrome-debug.sh setup
BOND_CHROME_DEBUG_PORT=9333 scripts/chrome-debug.sh open about:blank

Config via env: BOND_CHROME_DEBUG_PORT (default 9222), BOND_CHROME_DEBUG_PROFILE (default ~/.chrome-debug), BOND_CHROME_BIN, BOND_CHROME_DEBUG_KEEPALIVE (1 = relaunch on quit), BOND_CHROME_MCP_NAME (default bond-chrome-devtools). macOS only.

Standing rules

SessionStart prints shared/standing-rules.md into every session — the rules that used to live in a personal ~/.claude/CLAUDE.md, so the plugin carries them instead of the machine. A plugin has no declarative way to ship always-on instructions (skills and agents load on demand, and there is no auto-loaded plugin CLAUDE.md), so a hook is the mechanism.

Set BOND_USER_NAME to the name replies should open with; it falls back to git config user.name, and the greeting rule is dropped when neither resolves. The name is never committed — this repo is public.

shared/permissions-readonly.json is a read-only allowlist — the git reads (status, log, diff, show, branch, rev-parse), ls, wc, jq, head, tail, pnpm exec repograph, pnpm tasks report, pnpm tasks blockers and node --test: the calls that look at a tree without changing it. A plugin cannot apply permissions, so bond cannot switch them on for you — copy the permissions.allow entries into a project's .claude/settings.json (or the uncommitted .claude/settings.local.json). Until then every one of those calls is approved by hand, one at a time.

Project profile

Commands are not Bonliva-only. shared/project-profile.md resolves, per repo, the PR host, the base branch, whether there is a Jira tracker at all, and who the reviewers are. A repo can state its own answers in .bond/project.json; otherwise they are inferred from the origin remote. Outside Bonliva the tracker resolves to none, and /implement takes a free-text task, cuts a <type>/<description> branch and opens a PR with no ## Jira section.

Every command reads that profile rather than assuming a host or a tracker:

Host-flexible — /open-pr and /ship-pr work against Bitbucket Pipelines and GitHub Actions alike; the profile's Resolve PR coordinates and PR details and CI status procedures normalise both to one vocabulary, so no command branches on a host-specific status string.
Tracker-flexible — /implement and /start take free text where there is no Jira; /bond-bonliva:fix-qa does the same on the branch already checked out.
Guarded, not faked — /jira, /request-review, /publish-timelog and /log-plan genuinely need Jira, a Teams channel or Clockify. They say which prerequisite is missing and stop, rather than pretending to work.

/projects discovery is no longer hardwired to bonliva-*: set BOND_PROJECT_GLOB, or projectGlob in ~/.bond/projects.json.

Hooks

SessionStart runs hooks/standing-rules.mjs: the standing rules above. Registered with no matcher, so it fires on every start reason — startup, resume, clear, compact and fork alike. That is deliberate: rules that do not survive a compaction quietly stop applying halfway through a long session, and a matcher that failed to parse would drop them silently.
SessionStart and UserPromptSubmit run hooks/branch-guard.mjs: the branch the session opened on is recorded under <tmp>/bond/<session_id>.branch, and the first prompt submitted after the working tree has moved to another branch gets one line of context naming both branches and suggesting /clear. Once per recorded baseline — a session that carries two branches pays the first one on every turn of the second, but a reminder repeated every turn costs the tokens it is trying to save, so it is said once and re-armed by the next SessionStart (resume and compact reuse the session id, and the drift after one of those deserves a second word). A detached HEAD, a directory that is no git tree or an unwritable tmp means no nudge, never a blocked prompt. The rule is decide in that file, unit-tested in tests/branch-guard.test.mjs.
SessionStart runs hooks/node-guard.mjs: a tree that pins node in .nvmrc (or .node-version) gets one line of context when the shell its Bash calls land in runs another version — both versions and the PATH="$(nvm which <pin> | xargs dirname):$PATH" prefix every pnpm/node command then needs. Each Bash call is a fresh shell that does not carry nvm's PATH, so the prefix is per command rather than per session; met mid-session instead of at the start, the same fact costs a failed command per call (ERR_UNKNOWN_FILE_EXTENSION on every TypeScript entry point). A shorter pin covers the releases under it — 24 is satisfied by 24.16.0, 24.1 is not — while an alias only nvm could resolve (lts/*) and a tree with neither file say nothing. nvm is never invoked: the line names the prefix, it does not run it. The rule is check in that file, unit-tested in tests/node-guard.test.mjs.
PostToolUse runs prettier on any file edited via Edit, Write, or MultiEdit (no-op when prettier is not available in the project), then hooks/check-doc.mjs scans a just-written *.md|mdx|txt for AI signatures and reports the lines back.
PreToolUse on Bash runs hooks/check-commit.mjs: a git commit / gh pr … whose message carries an AI signature (Co-Authored-By naming a tool, Claude-Session:, "generated with") or a non-Conventional-Commits subject is blocked with the reasons. Patterns live in hooks/ai-breadcrumbs.mjs; see the authorship-conventions skill.
PreToolUse on Bash and the Bitbucket create_pull_request / create_draft_pull_request MCP calls runs hooks/check-pr.mjs: a PR whose title or body misses the shared Summary / Test plan shape, is not opened as a draft where one is required ("draft" in .bond/project.json, else a Bonliva repo: origin under bonliva/, a Bitbucket workspace: bonliva, or .bonliva-dev/project.json), or carries an AI signature is blocked with the reasons. See the pr-template skill and shared/pr-template.md. The rule lives in hooks/pr-template.mjs: it recognises the PR command only where the shell would run one — not inside a heredoc body, a quoted string or a comment — and treats only the configured Jira project keys as ticket ids, so UTF-8 and SHA-256 are prose.
PreToolUse on Bash runs hooks/bash-budget.mjs: context only, never a decision — the command always runs. Ten calls in a row that each carry a single command get one line naming the three cheaper forms — chain the next ones with && or ;, issue them in one message, or hand the loop to a subagent; measured over thirty days in one repo, 6481 Bash calls averaging 1.6 KB of output, where the price is not that output but the whole conversation being re-read on every one of them. Four shapes whose output has no bound get one line naming the bounded form — git log without -n/--oneline, cat of one whole file, ls -R or find without -maxdepth, a test run without --reporter. At most one line per call and the batch nudge wins; the row is counted in <tmp>/bond/<session_id>.bash-singles, whose own mtime says whether the previous call came from a turn of its own — a counter written under a second ago means both calls were dispatched in one message, which is already the batching asked for, so that call does not lengthen the row. An unwritable tmp costs the batch nudge, never the call. Separators are read where the shell would run them, so "a && b" and a heredoc body carrying && are each one command. The rule is judge in that file, unit-tested in tests/bash-budget.test.mjs.
PreToolUse on the subagent dispatch — Agent, or Task where the harness still names it that — runs hooks/recon-router.mjs: context only, never a decision — the agent is dispatched either way. A prompt handed to the unnamed or the general-purpose agent that asks where something lives, what or who calls it, which file holds it or how it is wired gets one line naming who answers it cheaply — repo-scout where the working tree has one under .claude/agents/, otherwise Explore with a breadth, either on model: "haiku". The general-purpose agent pays that search in full and returns everything it read; the other two return the conclusion. A dispatch to a reader (Explore, repo-scout, caveman:cavecrew-investigator) that names no model gets one line asking for haiku; one that names a model has made the choice. So has a prompt that builds — one carrying implement, add, write, refactor, fix, update, create, migrate or edit as a word — since the agent that writes the code reads it on the way there. The rule is route in that file, unit-tested in tests/recon-router.test.mjs.
UserPromptSubmit, and PreToolUse on Bash / Write / Edit / MultiEdit / NotebookEdit and the Bitbucket create_pull_request / create_draft_pull_request MCP calls, run hooks/secrets-guard.mjs: a prompt carrying a live-looking secret — GitHub, Atlassian (API and Bitbucket access tokens), Figma, Slack (tokens and webhook URLs), OpenAI/Anthropic, AWS (key IDs and secret keys), PEM and PGP private keys, Telegram bot tokens, database URIs with an inline password (Postgres, MySQL, MongoDB, Redis, AMQP), JWTs — is blocked before it is stored in the session, naming the kind and never the value and without echoing the prompt back (suppressOriginalPrompt); #allow-secret sends it anyway. A tool call that would write a literal secret into a file git tracks, a commit, a gh body (inline, or in the --body-file / -F file it sends), a pull request title or description or a curl line is blocked, unless the file already held that secret; a gitignored file, a lone echo / printf / cat into a gitignored .env*, claude mcp add outside project scope, a $VAR reference, a placeholder and a localhost dev URI pass. Unit-tested in tests/secrets-guard.test.mjs.
SessionStart, PreCompact and SessionEnd run hooks/session-memory.mjs: save (PreCompact, SessionEnd) reads the transcript and keeps the last five prompts, each cut to one line, the files the session edited and its branch in ~/.claude/bond/sessions/<repo>-<path>.json; restore (SessionStart) prints that note to the next session in the same directory — on startup or resume only, never after a compaction or a clear (the summary already carries it), never to the session that wrote it, and not once it is a week old. Small on purpose, because whatever SessionStart prints is re-read on every turn: five prompts of at most 160 characters, and a file list cut, with a "+N more" tail, so it never takes the note past 1 KB. An empty session does not overwrite a real one's note. The rules are digest and render, unit-tested in tests/session-memory.test.mjs. Adapted from everything-claude-code's memory-persistence hooks.
PreToolUse on every tool runs hooks/suggest-compact.mjs: context only. At the 50th call since the last compaction, and every 25th after, one line suggests /compact if a phase just ended — auto-compaction fires wherever the window fills, a chosen one keeps what the next phase needs. PreCompact resets the count in <tmp>/bond/<session_id>.tool-calls. The rule is judge, unit-tested in tests/suggest-compact.test.mjs. Adapted from everything-claude-code's strategic-compact hook.

Tests

The hook rules are unit-tested with the Node test runner — no dependencies, no install step. Covered: the two matchers the commit and PR hooks decide on — whether a command really runs git commit or gh pr, and whether a call really opens a pull request — along with the AI-signature patterns they share with check-doc.mjs; the ticket-key rule; the standing-rules rendering; and the four context hooks through their decision functions, decide (branch-guard), judge (bash-budget, suggest-compact), digest/render (session-memory), route (recon-router) and check (node-guard), each with its wrapper driven over stdin as well. context-audit.py is run against the hand-sized transcript under tests/fixtures/projects/, every SKILL.md is held to its size limit and to the references/ files it links, and check-commit.mjs is driven end to end over stdin:

node --test 'tests/**/*.test.mjs'

bond-cockpit is tested by Claude Code's own plugin runner — the cache view directly, and the status line and pane on the terminal and desktop surfaces:

claude plugin validate plugins/bond-cockpit && claude plugin test plugins/bond-cockpit

Skills

readable-code-structure — splits long functions into small named ones and replaces awkward/clever control flow (search loops, N+1 in loops, nested ternaries, flag params) with plain expressions. Triggers on clean-up/refactor/"make this readable" requests and during review. Also carries the two mechanical rules that share its trigger exactly: brace every control body (one-liners and guard clauses included), and collapse repeated passes over one collection. Bundled under skills/readable-code-structure/.
comment-hygiene — comments the why, deletes comments that restate the code, strips ticket IDs, and handles tool directives / TODOs / dead code / license headers. Triggers on writing or reviewing comments and on clean-up/"remove comments" requests. Bundled under skills/comment-hygiene/.
testing-behavior — writes tests that pin the caller's contract, not the current implementation; refuses change-detector tests and tautologies, and stops to ask before enshrining suspicious behaviour. Triggers when adding, editing, or reviewing tests. Bundled under skills/testing-behavior/.
vertical-horizontal-review — enforces a two-pass code review: vertical (trace one feature through every layer) + horizontal (sweep every sibling of the kinds the change touches for drift). Project-agnostic. Triggers on "review this change/diff/branch/PR". Bundled under skills/vertical-horizontal-review/.
pr-template — enforces the one shared PR title + description format (Summary / Jira / Test plan) and the default reviewer list on every pull request, sourced from shared/pr-template.md. Triggers on "open/create/draft a PR" and manual create_pull_request calls. Bundled under skills/pr-template/.
woodpecker-cli — drives a Woodpecker CI server from the terminal: auth (WOODPECKER_SERVER / WOODPECKER_TOKEN), the command map, step-scoped log reading for failed pipelines, and lint / exec for .woodpecker.yaml. Triggers on "woodpecker", "pipeline logs", "why did the pipeline fail". Bundled under skills/woodpecker-cli/.
authorship-conventions — naming and attribution for every git artefact: Conventional Branch <type>/<description>, Conventional Commits subject, prose why body, one human owner, zero AI signatures (no Co-Authored-By naming a tool, no Claude-Session:, no "generated with") in commits, PR bodies/comments or docs — plus the rename trap: renaming a branch after its PR is open closes the PR. Bonliva repos keep the <prefix>/<KEY> branch shape bond imposes; everywhere else the spec wins. Backed by the check-commit / check-doc hooks. Triggers on checkout -b, "commit", "amend", "open a PR", "write the ADR/plan/README". Also decides which of the two gh accounts pushes — the active one is machine-global, so another session may have moved it since. Bundled under skills/authorship-conventions/.
routing-model-and-effort — picks a (model, effort) pair per task phase: opus/medium by default, high for a change over five files, across modules or untested, fable for planning only on the hard predicates, opus for every build unless a model is named, a fresh bond:effort-<tier> subagent whenever the pair differs from the session, and recon — search, callers, a docs lookup, one check run — spawned on haiku. Triggers when a task will change files or needs a plan, and when a model or effort comes up. Bundled under skills/routing-model-and-effort/.
routing-code-review — routes the /code-review level off the diff: high by default, medium/low when the diff is small, single-module, tested and risk-free, a question for max, and ultra only recommended (the user launches and pays for it); --fix for our own diff, --comment/--post on the user's word. Triggers when a review is about to be launched. Bundled under skills/routing-code-review/.
context-cost — what a screenshot, a whole-file read or an unbounded command costs once the session carries it, and the cheaper form that answers the same question. Measured: cache reads are 65 % of weighted cost, and the 15 largest sessions on one machine carried 42 % of its usage. Bundled under skills/context-cost/.
verification-loop — runs the repo's own build, typecheck, lint and tests (commands read from CI config first, then package.json/Makefile), scans the added lines for secrets and debug leftovers, and reports one READY / NOT READY line; a gate the repo lacks is n/a, never PASS. Sits before finishing-with-code-review. Bundled under skills/verification-loop/.
security-checklist — a checklist over the changed lines only, by section (secrets, input, injection, authn/authz, web, uploads, exposure, abuse), each picked by what the diff touches; findings as file:line with the attack and the fix. Bundled under skills/security-checklist/.
linkedin-writing — voice and format for LinkedIn posts and articles: facts from the repo, numbers checked against the vendor's docs, attribution left to the author, plain text for posts, one cover-image prompt with its technical description, and how to fill LinkedIn's editors in Chrome without publishing. Used by /linkedin and /linkedin-draft. Bundled under skills/linkedin-writing/.
finishing-with-code-review — a task that changed code ends with the routed review, the findings applied, the tests re-run and the fixes committed, then the recap; a docs-only diff is the one skip. Triggers before a recap, before a PR, and on "ship it". Bundled under skills/finishing-with-code-review/.

Agents

effort-low / effort-medium / effort-high / effort-xhigh / effort-max — one agent per reasoning effort level; the caller passes model at call time. effort-high, effort-xhigh and effort-max fall back to model: opus when the caller omits it; effort-low and effort-medium fall back to the session default subagent model, so a cheap tier is not silently run on the most expensive model. Used by the routing-model-and-effort skill because effort is only settable through an agent definition. Bundled under agents/.
test-runner — runs one test, typecheck or lint command on haiku at low effort and returns only the failures: the runner's own counts on line 1, then at most 40 path:line: message lines and … N more. A command that cannot start comes back as the first 5 lines of stderr. Hand it every check whose full output would otherwise land in the main context. Bundled under agents/.
ci-diagnose — reads one failed pipeline (Woodpecker, GitHub Actions or Bitbucket URL) on sonnet at medium effort and returns per failed step its class — flaky, infra, code, or pre-existing on the base — a file:line cause and at most 5 log lines. Read-only; /fix-ci acts on it. Bundled under agents/.
pr-watch — watches one PR until it can merge, on opus at medium effort: polls its CI every ~5 minutes, sorts each red check as /fix-ci does, fixes and pushes a cause the branch's own code made in the worktree it is given, and loops on the re-run until green, until only pre-existing, infra or human-owned causes are left, or until its rounds or deadline run out. Never merges, approves, force-pushes or reruns a cause twice. The standing rule «Waiting goes to an agent» sends every wait on a PR's CI through it. Bundled under agents/.
pr-status — reads one PR once on haiku at low effort, GitHub or Bitbucket: state, mergeable, the CI verdict with one root-cause line per failed check, the review decision, and every unhandled inline thread, review body and conversation comment with its id (minus the ids the caller already handled). Read-only — never replies, resolves, reruns or polls. /ship-pr reads each settled round and its final state through it. Bundled under agents/.
pr-review — reviews one open PR's diff on opus at high effort, GitHub or Bitbucket: reads each hunk with its callers, verifies every finding before reporting it, and returns at most 15 ranked findings with file:line and the input that breaks it. Read-only — never edits, pushes or comments. Paired with security-review through shared/pr-review-flow.md; /ship-pr runs the pair right after the PR is opened, before the browser check. Bundled under agents/.
security-review — reviews a diff, PR or path for security defects on opus at high effort: access control and IDOR, injection, auth and sessions, SSRF, XSS, secrets, races on money, data exposure, and an audit when a lockfile changed. Verifies each finding and returns at most 15 with file:line, the attack and the fix. Read-only. Always runs paired with pr-review through shared/pr-review-flow.md (/ship-pr, /sweep-pr); a critical or high finding from either blocks. Bundled under agents/.

Installation

From a marketplace (recommended)

# In Claude Code
/plugin marketplace add devmaxxx/bond
/plugin install bond@devmaxxx

Local dev

Add this directory as a local marketplace:

/plugin marketplace add /Users/max/Documents/projects/bond
/plugin install bond@devmaxxx

Layout

bond/
├── .claude-plugin/
│   ├── plugin.json         # plugin manifest
│   └── marketplace.json    # marketplace entry (single-plugin repo)
├── commands/               # slash commands
├── skills/                 # each SKILL.md ≤ 3 KB; the detail sits in <skill>/references/
│   ├── readable-code-structure/  # small named functions, plain control flow, braces, one pass
│   ├── comment-hygiene/    # comment the why, delete the what
│   ├── testing-behavior/   # test the contract, not the implementation
│   ├── vertical-horizontal-review/  # two-pass review: depth + sibling sweep
│   ├── pr-template/         # one shared PR title + description + reviewers
│   ├── woodpecker-cli/      # Woodpecker CI CLI: auth, commands, lint/exec
│   ├── authorship-conventions/  # branch/commit/PR/doc naming, attribution, gh account
│   ├── routing-model-and-effort/  # (model, effort) pair per task phase
│   ├── routing-code-review/  # /code-review level, target and flags per diff
│   ├── context-cost/        # what a read/screenshot costs once the session carries it
│   │   └── scripts/context-audit.py  # per-session tool-result bytes, compactions, results over 40 KB
│   ├── verification-loop/   # build, types, lint, tests, diff scan → READY / NOT READY
│   ├── security-checklist/  # per-section security questions over the changed lines
│   └── finishing-with-code-review/  # every code task ends with the review
├── agents/
│   ├── docs-explorer.md     # look up official docs before using a third-party API
│   ├── test-runner.md       # run one check, return only the failures
│   ├── pr-status.md         # one PR's CI, review and unhandled comments, compact
│   ├── pr-review.md         # one PR's diff reviewed, verified findings ranked
│   ├── security-review.md   # security defects in a diff, PR or path, verified
│   ├── ci-diagnose.md       # one failed pipeline: class, cause, short excerpt
│   └── effort-{low,medium,high,xhigh,max}.md  # one agent per effort level
├── shared/
│   ├── implement-flow.md   # shared procedures used by /implement and /fix-qa
│   ├── merge-conflicts.md  # detect, rebase or merge, resolve, prove — ship-pr, rebase, sweep-pr
│   ├── project-profile.md  # per-repo host, base, tracker, reviewers
│   ├── standing-rules.md   # always-on rules, printed by the SessionStart hook
│   ├── pr-review-flow.md   # code + security review as one pair — ship-pr, sweep-pr
│   ├── pr-template.md      # single source of truth for PR title + description
│   └── permissions-readonly.json  # read-only allowlist to copy into a project
├── scripts/
│   ├── disk-analyze.sh     # disk usage report behind /disk-analyze
│   └── chrome-debug.sh     # fallback: debuggable Chrome LaunchAgent + its MCP
├── hooks/
│   ├── hooks.json
│   ├── format-file.sh      # PostToolUse: prettier on the edited file
│   ├── shell.mjs           # is this command really *running* X?
│   ├── standing-rules.mjs  # SessionStart: print the always-on rules
│   ├── render-rules.mjs    # what the session actually reads
│   ├── branch-guard.mjs    # SessionStart + UserPromptSubmit: the branch moved under this session
│   ├── bash-budget.mjs     # PreToolUse: a row of one-command calls, output with no bound
│   ├── recon-router.mjs    # PreToolUse: who answers a "where is X" prompt cheaply
│   ├── node-guard.mjs      # SessionStart: the shell node is not the version .nvmrc pins
│   ├── session-memory.mjs  # PreCompact/SessionEnd save, SessionStart restore: last session's note
│   ├── suggest-compact.mjs # PreToolUse: a /compact reminder at 50 calls and every 25 after
│   ├── ai-breadcrumbs.mjs  # shared AI-signature patterns
│   ├── check-commit.mjs    # PreToolUse: block git commit / gh pr with a signature
│   ├── pr-template.mjs     # the PR rule: command matcher, ticket keys, sections
│   ├── check-pr.mjs        # PreToolUse: block a PR that breaks the shared template
│   └── check-doc.mjs       # PostToolUse: flag a written md/txt with a signature
├── tests/
│   ├── pr-template.test.mjs  # node --test 'tests/**/*.test.mjs'
│   ├── render-rules.test.mjs
│   ├── branch-guard.test.mjs
│   ├── bash-budget.test.mjs
│   ├── recon-router.test.mjs
│   ├── node-guard.test.mjs
│   ├── context-audit.test.mjs
│   ├── skill-size.test.mjs
│   ├── shell.test.mjs
│   └── fixtures/projects/    # a transcript sized by hand, read by context-audit.test.mjs
├── plugins/bond-bonliva/   # Bonliva-only companion plugin (enable per repo)
├── plugins/bond-cockpit/   # prompt-cache status line + pane mod (function hooks)
├── plugins/bond-oss/       # open-source library create/audit/demo/release (enable globally)
│   ├── .claude-plugin/plugin.json  # depends on bond
│   ├── commands/           # fix-qa, log-plan, projects, publish-timelog, request-review, set-reviewers, setup-plugin, teams-post
│   ├── data/               # bb-members, teams-users, pr-review-card
│   ├── scripts/teams-post.sh
│   ├── shared/             # symlinks into bond: project-profile, implement-flow, jira
│   └── .mcp.json           # MCP server template (installed via /bond-bonliva:setup-plugin)
├── LICENSE
└── README.md

License

MIT — see LICENSE.

Navigation Menu

Repository navigation

About

Repository files navigation

bond

Commands

bond-bonliva (Bonliva-only companion)

bond-cockpit (job, prompt-cache status line and pane)

bond-beauty-crm (beauty-crm-only companion)

bond-oss (open-source library companion)

MCP Servers

Teams channel webhook

Browser access

Chrome debug (fallback, for the chrome-devtools MCP)

Standing rules

Project profile

Hooks

Tests

Skills

Agents

Installation

From a marketplace (recommended)

Local dev

Layout

License

About

Releases

Packages

Contributors

Languages

Name		Name	Last commit message	Last commit date
.claude-plugin		.claude-plugin
.claude/commands		.claude/commands
.codex		.codex
agents		agents
commands		commands
hooks		hooks
plugins		plugins
scripts		scripts
shared		shared
skills		skills
tests		tests
.gitignore		.gitignore
AGENTS.md		AGENTS.md
CLAUDE.md		CLAUDE.md
LICENSE		LICENSE
README.md		README.md

Latest commit

History

Folders and files

Repository files navigation

bond

Commands

bond-bonliva (Bonliva-only companion)

bond-cockpit (job, prompt-cache status line and pane)

bond-beauty-crm (beauty-crm-only companion)

bond-oss (open-source library companion)

MCP Servers

Teams channel webhook

Browser access

Chrome debug (fallback, for the chrome-devtools MCP)

Standing rules

Project profile

Hooks

Tests

Skills

Agents

Installation

From a marketplace (recommended)

Local dev

Layout

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages