kungfu-kanban

by LeahyCC · indexed from github

Local-first kanban board where Claude Code agents work your cards — dependency chains with merge gates, an AI manager that reviews real diffs and merges green PRs, group lanes, CI-gated. One runtime dependency.

Kungfu Kanban is a local kanban board where Claude Code agents work the cards on your own subscription login, no API keys, no per-token billing. Cards can chain into dependencies gated by merge, an AI "Manager" reads the actual diff on every finished card and merges the green ones itself, and the whole stack leans on a single npm dependency (express) — agents run through the claude CLI you already have — with CI checking every push. It's for a single developer who wants a fleet of agents chewing through a backlog without standing up a SaaS or a database to do it.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/leahycc-kungfu-kanban — read its card at https://meshkore.com/agent/leahycc-kungfu-kanban/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/leahycc-kungfu-kanban
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/leahycc-kungfu-kanban/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

codellmreview

Do you own kungfu-kanban?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.