ApexYard plugin
An ops repo for Claude Code: tickets, the Rex reviewer and a closed merge gate take agent code to production under human control.
- 544 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Hooks and sub-agents change code, commits and merges across several repositories.
Install
- Works in
Manual install
gh repo clone your-org/apexyardStep 2 of the quick start: first fork on GitHub, then clone, `git remote add upstream https://github.com/me2resh/apexyard.git` and `/setup`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks and sub-agents change code, commits and merges across several repositories.
This is third-party code. Review the repository files before installing.
What it does
ApexYard deploys as a fork that governs a portfolio of your repositories. Every change starts with a ticket, an independent reviewer Rex checks the pull request, and the merge gate stays closed until a named human approves the exact commit. Inside are 20 roles across six departments, 60 shell hooks that enforce the rules mechanically (ticket-first edits, migrations, secrets scanning), 69 skills such as `/setup`, `/code-review`, `/migration` and `/launch-check`, 23 sub-agents and 22 rule files. All of it is plain markdown and shell with no service to run.
Who it is for. Teams and solo developers who hand code writing to agents and want to keep review, decisions and release control.
Good fit when
- An agent writes a lot of code and review must be mandatory before merge.
- Technical decisions get lost in chat and need to be kept as records.
- A database schema change requires a ticket and a rollback plan.
- Several projects must sit in one registry with shared rules.
Not a fit when
- You need a quick one-file edit with no process.
- The team is not ready to adopt tickets and two approval markers.
- A cloud service is wanted rather than a fork of files.
Example request
/setup Configure ApexYard for my four-person TypeScript team and register two projects.Limitations
The framework imposes a strict process: hooks block edits without a ticket and merges without approval, so it slows work at first and needs configuring through `/setup`. The main driver is Claude Code; opencode, pi and Codex need adapters. Configuration lives in a local `onboarding.yaml` that must not be committed, with a hook guarding it. Upstream updates come in via `/update`, and conflict resolution stays with you.
How to disable. Retire the fork: remove hooks and rules from the project or delete the fork itself. If you installed from the marketplace, run `/plugin uninstall`.
FAQ
How do I start?
Fork, clone, add `upstream` and run `/setup` in Claude Code.
Who is Rex?
An independent reviewer who checks every pull request. Merge needs approval from Rex and a named human on the exact commit.
Is a running service needed?
No. It is markdown and shell with no external services or hosting lock-in.
How do I pull updates?
With `/update`: it previews the diff, uses a sync branch and guides version migrations.
Does it work with other agents?
Adapters connect opencode, pi and Codex. The main driver is Claude Code.
Discussion
No questions or reviews yet.
Related
PluginsClaude Code kit with eight phase agents, 21 skills and hooks that keep the agent inside set limits.
A Claude Code plugin that hands a task to a local no_human and reviews a branch with a reviewer that never saw the coder's session
Six commands for Claude Code, Codex and Cursor: the main session holds context while fresh agents review the problem and diff.
Xylocopa is a visual orchestrator for Claude Code agents: GTD tasks, parallel agents in git worktrees, phone approvals.
A plugin makes the agent explain its code and, before a push, ask questions so you understand what you are merging.
A workflow template for Claude Code and five more agents: a backlog task, a diff review and a commit.
README in short
The README sets out the process idea, a comparison with working without the system, the contents of the set and a quick start via fork.