ForgeDock plugin
A CLI and Claude Code plugin taking GitHub issues through checks, plan, code, review and CI to merge, in parallel lanes
- 119 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- The agent writes code, opens pull requests and merges into project branches without a human at each step
- The engine uses GitHub tokens and spends money on the Claude account
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/forgedockDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent writes code, opens pull requests and merges into project branches without a human at each step
- The engine uses GitHub tokens and spends money on the Claude account
This is third-party code. Review the repository files before installing.
What it does
ForgeDock takes GitHub issues all the way to merged pull requests. Each issue runs in its own lane in a fixed order: check whether it is real work, a plan with a frozen contract, implementation in an isolated worktree, a separate review against the contract, then a pull request, CI and merge. The engine, not the model, picks the next step. `forgedock orchestrate 41 42 43 --parallel 3` schedules a batch from `Depends on #N` lines, keeps several lanes busy and retries mechanical failures such as red CI and merge conflicts on its own. It asks a person only about product direction, spend, credentials and releases. State lives in issue comments on GitHub and in a run log, so work resumes after a crash. Changes land in a staging branch, and a release to the default branch follows a staging review with a marker that CI checks. In Claude Code the same flows are `/work-on 42` and `/orchestrate`. It runs on your Claude account and works with GitHub only.
Who it is for. Teams and solo developers with a GitHub issue queue who are ready to hand implementation and merging to agents while keeping product decisions.
Good fit when
- The tracker has dozens of dependent issues and a batch must run in `Depends on #N` order
- You want to check whether an issue is stale: already-fixed ones close with evidence and no code
- A release to the default branch must pass a staging review by reviewers for security, concurrency and auth
- A session dropped mid-run and you need to continue from what GitHub remembers
Not a fit when
- You need another code host: only GitHub is supported
- You have no Claude Code subscription or `ANTHROPIC_API_KEY`: the engine runs on your account
- A closed product cannot accept AGPL: proprietary use needs a separate commercial license
Example request
Run forgedock demo so I can see the whole pipeline on a throwaway repo, then show how to take issue 42 through /work-on 42.Limitations
You need Claude Code with a subscription or `ANTHROPIC_API_KEY`, an authenticated GitHub CLI and Node.js 18 or newer. The engine works only with GitHub. Costs come from your Claude account, and `forgedock stats --efficiency` helps estimate them. Autonomous merging into a staging branch and releases raise the price of a mistake, so mark risky paths in `forge.yaml`. The integration-test check before a release reports SKIP until you configure `verification.integration_tests`. The core is AGPL-3.0, with a commercial license for closed use.
How to disable. Remove the package with npm uninstall -g forgedock and the plugin through /plugin. Delete forge.yaml and the staging branches by hand, and revoke any GitHub and Claude tokens you made for the agent.
FAQ
How can I try it without my own repo?
Run `npx forgedock demo`: it creates a throwaway repository and runs the pipeline from issue to merge. You need Claude Code, an authenticated GitHub CLI and Node.js 18.
How do I run it on my project?
Install `npm install -g forgedock`, run `forgedock` to check the environment and create `forge.yaml`, then `forgedock run-issue 42` for one issue or `forgedock orchestrate 41 42 43 --parallel 3` for a batch.
What does the agent decide and what goes to a person?
It retries mechanical failures on its own: red CI, merge conflicts, engine errors. Product direction, spend, credentials, customer-facing actions and releases always go back to a person.
Where do changes merge?
Lanes merge into a staging branch or `milestone/*`. A release to the default branch follows a staging review that posts a `FORGE:GATE_PASS` marker checked in CI.
Does it work with OpenCode?
Yes. Claude Code is the main runtime and OpenCode is supported through a separate guide in the project docs. GitHub is the only code host.
Discussion
No questions or reviews yet.
Related
PluginsA plugin with ready, go and migration commands: it settles what you want first, then builds and verifies the result
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
LoopForge Local adds a role-based dev workflow to Claude Code, Codex and Cursor: analysis, design, code, review and tests.
A Claude Code plugin: 39 commands for PRs, review, commits and specs, nine expert roles and hooks, in eight language versions
Software factory installer for Claude Code and Codex: a GitHub Issues queue, skills, gates and merges done only by a human.
A Claude Code plugin: cards dropped into Ready on a GitHub Projects board go through build, QA and review and come back as pull requests
README in short
The README explains that ForgeDock turns GitHub issues into merged pull requests and shows a 30-second start. It then gives 30-day figures from its own repository, examples of defects the gates caught, a candid list of what breaks, how a lane, a batch and a release work, a table of what works today, questions and the AGPL-3.0 license notes.