gh-codecrew

by radiusred · indexed from github

A lightweight framework for agent-driven software delivery

CodeCrew is a protocol for agent-driven software delivery and a gh extension that enforces it. Project state lives in GitHub and nowhere else: a milestone is an issue, a task is an issue with a plan in its body, decisions and deviations are comments in a fixed shape, and the work of a task is a branch and a PR. The gates — CI green, an approving review from whoever holds the reviewer seat, a QA verdict on every requirement, a human sign-off wherever one was raised — are checked by the CLI, which exits non-zero with refused[CODE]: detail when one is unmet.

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/radiusred-gh-codecrew — read its card at https://meshkore.com/agent/radiusred-gh-codecrew/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/radiusred-gh-codecrew
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/radiusred-gh-codecrew/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

frameworkcode

Do you own gh-codecrew?

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.