Wire Claude Code into every stage of a repository's lifecycle with one install command. Claude triages every issue, implements approved work, reviews every PR, safely auto-merges minor updates, runs weekly maintenance, and drafts releases — as GitHub Actions, with Claude Code OAuth as the default auth, no servers required.
GitHubAI is three things at once:
- A framework — reusable, hardened workflows and a composite action you reference at a ref, so every adopting repo upgrades by bumping one tag.
- A template — repo-type profiles (library, webapp, service, cli, github-action, docs, data, template) that set standards based on what your repo is and what it's for.
- A GitHub App — a multi-tenant webhook relay that routes org-wide events into the same workflows, with org-level policy and a read-only activity dashboard, for orgs that would rather install once than add stubs everywhere.
flowchart LR
I[Issue opened] --> T[Claude triages<br/>labels, dedupe, questions]
T -->|"claude:implement" label| M[Claude implements<br/>branch + PR]
M --> R[Claude reviews<br/>standards + inline findings]
H[Human PRs] --> R
D[dependabot / renovate] --> A[Claude safety gate<br/>structured verdict]
R -->|minor + clean| A
A -->|approve + auto-merge<br/>waits for checks| G[Merged]
S[Weekly cron] --> W[Claude maintenance<br/>docs drift, TODOs, health]
V[Tag push] --> N[Claude release notes]
Every box runs anthropics/claude-code-action@v1 authenticated OAuth-first, and every prompt is grounded in your repo's resolved standards: framework defaults ← repo-type profile ← your .github/githubai.yml.
# from your repo's root
curl -fsSL https://raw.githubusercontent.com/bamr87/githubai/main/setup/install.sh | bash -s -- --labels
# authenticate: Claude Code OAuth token is the default for every workflow
claude setup-token
gh secret set CLAUDE_CODE_OAUTH_TOKENThen install the Claude GitHub App on the repo, set repo.purpose in the generated .github/githubai.yml, and open an issue — Claude triages it within minutes. Full walkthrough: docs/getting-started.md.
| Workflow | Trigger | What Claude does |
|---|---|---|
claude.yml | @claude mention, issue assignment | Interactive: answers, fixes, implements whatever you ask |
claude-triage.yml | issue opened/reopened | Labels type/priority/size, finds duplicates, asks clarifying questions |
claude-implement.yml | claude:implement label | Builds the issue on a branch, runs your tests, opens a PR |
claude-review.yml | PR opened/ready, claude:review label | Reviews against your repo type's standards, inline comments + verdict |
claude-auto-merge.yml | claude:auto-merge label, trusted bot PRs | Read-only safety verdict; approves and enables auto-merge only for low-risk minor changes |
claude-maintenance.yml | weekly cron, manual | Docs drift, TODO sweep, dependency report, stale nudges, health report |
claude-release.yml | tag push, manual | Categorized release notes; version-bump release PRs |
Each workflow doubles as a reusable workflow (workflow_call), which is exactly how installed repos consume them — details in docs/workflows.md.
The profiles encode what "good" means per repo type — a library gets semver-compatibility review focus, a webapp gets migration-safety and security focus, a GitHub Action repo gets injection and pinning focus. Your .github/githubai.yml picks the type, states the purpose, and overrides anything:
repo:
type: librarypurpose: "Date-parsing library consumed by our billing services."automation:
auto_merge:
enabled: true # dependabot patch bumps merge themselves when greenstandards:
test_command: npm testSchema reference: docs/configuration.md. Labels are the control plane: claude:implement authorizes work, claude:auto-merge nominates a PR for the merge lane, claude:skip opts anything out, claude:needs-human is Claude escalating to you.
Every workflow authenticates with CLAUDE_CODE_OAUTH_TOKEN (from claude setup-token — included in Claude subscriptions) and falls back to ANTHROPIC_API_KEY only when the OAuth token is absent. One org-level secret can power every repo. Threat model, permissions, and the auto-merge safety design: docs/security.md.
.github/workflows/ the framework: reusable claude-*.yml + this repo's CI
actions/load-config/ composite action resolving profile + repo config
profiles/ repo-type standards (the "based on type and purpose" part)
template/ what the installer copies into adopting repos
setup/install.sh the one-command installer
app/ GitHub App: manifest, multi-tenant relay, operations docs
docs/ getting started, configuration, workflows, security, architecture
tests/ self-tests keeping the framework honest
This repo runs its own framework — the workflows above are live here, configured by .github/githubai.yml with the template profile. If the machinery doesn't work on itself, it doesn't ship.
Installing stubs in fifty repositories is fine; governing fifty repositories from fifty files is not. App mode swaps the per-repo event stubs for one GitHub App: events reach a small Cloudflare Worker that verifies them, applies your organization's policy, and fires repository_dispatch into each repo's workflows. What it does not change is where Claude runs or whose token it uses — execution stays in each repository's own Actions with that repository's own CLAUDE_CODE_OAUTH_TOKEN. The relay holds no code, no credentials, and no model traffic (full inventory).
Org policy lives in your own .github repository as .github/githubai-org.yml and is subtractive by design — it can keep events from reaching repositories, never grant a repository something its own config disabled:
org:
repos:
exclude: ["legacy-*"] # these repos see no automationautomation:
auto_merge:
enabled: false # no repo in this org enters the auto-merge laneSigning in to the relay shows what it did with every delivery — dispatched, ignored, blocked by policy, or failed — which is the one question a router owes you. Deploy it with app/OPERATIONS.md; it runs on Cloudflare's free tier.
The Django/React application that previously lived here (last release v0.5.3) was replaced by this framework; every v0 capability has a lighter successor. See docs/migration-v0.md.