Coding agents only see one repo at a time, and they forget everything between sessions. kbee builds a cited knowledge base of how your repos fit together. Then it takes a feature from idea to cross-linked pull requests in every repo it touches.
Works in any agent that reads Agent Skills: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and more.
Real systems span an API, a web app, shared types and workers. A change that looks safe in one repo breaks a consumer in a repo the agent never opened.
kbee gives every agent session the same map: which repos exist, what each one owns, and who produces and consumes each API, event and type.
kbee-init builds the KB from your repo links and shows you one summary to approve. kbee-feature then runs every stage below, and you can stop and resume whenever you like.
kbee-specAcceptance criteria, affected repos, contracts touched.
kbee-planTasks per repo, producers before consumers, each with its test.
kbee-buildTest-first on kbee/<slug> branches, one repo at a time.
kbee-reviewCorrectness, plus every changed contract checked against its consumers.
kbee-shipPushes branches and opens cross-linked PRs with merge order.
kbee-syncKeeps the KB true after the PRs merge.
Review loops back to build for up to 3 rounds. Run kbee-feature again and it resumes from features/<slug>/status.json.
Each claim points at a repo, commit, file and line range. Facts without a citation are left out.
[shop-api@a1b2c3d:src/orders.ts:7-11]kbee rereads every citation and checks it against the code before the fact stays in.
When a repo moves on, kbee knows which KB sections cite the files that changed.
kbee proposes fixes and never rewrites the KB silently. Bookkeeping such as feature progress saves on its own.
Changes from unmerged branches wait in pending.md until their PRs merge.
Questions it can't answer go into gaps.md. It doesn't guess.
Your team shares the KB by pushing and pulling. There's no server, database or account. Anyone can open it and read it, and so can any agent.
Ask it anything with kbee-kb, for example “which repos consume POST /orders?”, and the answer comes back with citations into the code.
shop-kb/ system-map.md # repos, ownership, links (Mermaid) repos/<repo>/ # overview + conventions contracts/ # APIs, events, types: producer → consumers decisions/ # architecture decisions and why features/<slug>/ # spec, plan, status, review gaps.md # open questions manifest.json # repos + the commit each was synced at
kbee-initSet up a KB, or join your team's existing onekbee-featureRun every stage, start to finishkbee-specSpec, including the affected repos and contractskbee-planTasks per repo, producers before consumerskbee-buildTest-first implementation on kbee/<slug> brancheskbee-reviewCorrectness, and contract checks against every consumerkbee-shipPush and open cross-linked PRs, after one yeskbee-syncKeep the KB true, including after mergeskbee-kbAsk, expand, add a repo, or fix the KBYou need git and a coding agent. Node 18+ (for the bundled citation and staleness helper) and the GitHub CLI are optional. v1 is sized for up to about 10 repos of up to about 100k lines each.
Install the skills, point kbee-init at your repos, and approve one summary.