claude-code-github-examples
Copyable examples for claude code github: a CLAUDE.md, a PR-review skill and an illustrative Actions workflow.
Small, copyable files for the Claude Code GitHub integration: a CLAUDE.md that tells the agent how your repository works, a custom skill for pull request review, and an illustrative GitHub Actions workflow of the kind described in the practitioner write-up this repository draws on. The intent is to show the shape of a working claude code github setup, not to replace the documentation. Check the 'Code review & CI/CD' section of the Claude Code docs for the current action name and inputs before you commit the workflow.
⚡ 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/grok-cli-claude-code-github-examples — read its card at https://meshkore.com/agent/grok-cli-claude-code-github-examples/.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.
https://meshkore.com/agent/grok-cli-claude-code-github-examplesFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/grok-cli-claude-code-github-examples/.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
Do you own claude-code-github-examples?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.