Keep a customized fork current without merge commits or untested promotions.
Patchlane rebuilds an integration branch from an upstream release or branch, reapplies focused patch branches, runs your existing CI, and promotes the exact tested commit.
From a clone of your GitHub fork, install the Patchlane agent skills:
npx patchlane agentsThen ask your coding agent:
Set up this fork with Patchlane.
The setup skill inspects the repository, asks which upstream release or branch to track, and shows its complete plan before pushing or rewriting branches. It then creates the patch stack, validates it, and guides the first tested promotion.
For agent development after setup, create a complete composed workspace instead of editing a raw lane:
npx patchlane workspace create --lane patch/product
# work and test in the printed directory
npx patchlane workspace status --json
npx patchlane workspace land --dry-runPrefer to configure it yourself? Follow the manual setup guide. Already using an earlier Patchlane version? Use the migration guide.
- Resolve an explicit source such as
release:latestorbranch:main. - Rebuild
sync/integrationfrom that source. - Replay independently based patch branches in order.
- Run the fork's existing CI on the generated branch.
- Promote only the exact SHA that passed CI.
The promoted base and sync branches are generated output. Fork-owned changes belong on patch/* branches. For agent development, use a composed workspace so every lane, workflow, test, and local tool is visible while commits remain assignable to one lane.
npm install
npm testModel-backed skill evals are opt-in; see evals/README.md.
MIT