autoconverge

Drives a draft GitHub PR to convergence through autonomous review and fix rounds.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill autoconverge-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autoconverge
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/skill-archive/autoconverge
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill autoconverge-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Iterating on a draft pull request through repeated code reviews, bug audits, and bot feedback is slow and manual. This Skill automates the entire loop: it runs parallel review lenses, applies one-commit fixes, and gates readiness on Bugbot, Copilot, and Codex confirmations until the PR is ready. ## Core Features & Use Cases - Autonomous convergence loop: Runs three parallel review lenses (code-review, bug-audit, self-review) per round and lands fixes in single commits via a workflow script or portable in-session driver. - Terminal reviewer gates: Treats Cursor Bugbot, GitHub Copilot, and Codex reviews as confirmation gates before marking the PR ready, with quota and outage handling for each. - Multi-PR fan-out and reporting: Converges several PRs in parallel worktrees and publishes a closing HTML convergence report with an idempotent PR comment. - Use Case: A developer opens a draft PR and says "/autoconverge"; the Skill enters a worktree, runs review-fix rounds, verifies Copilot findings with executed checks, and marks the PR ready once all reviewers are clean on the same HEAD. ## Quick Start Ask the AI to run /autoconverge on your draft pull request URL to drive it to ready autonomously.

Frequently Asked Questions about autoconverge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I autonomously converge a draft GitHub PR?▼

Invoke /autoconverge with a PR URL or number. The Skill enters a worktree on the PR branch, runs review-fix rounds through a workflow script or portable driver, and marks the PR ready once all reviewer gates are clean on the same HEAD.

What review tools does the autoconverge workflow use?▼

Each round runs three parallel lenses: code-review, bug-audit, and self-review. Terminal confirmation gates use Cursor Bugbot, GitHub Copilot, and Codex reviews before the ready transition.

Can autoconverge run without the Workflow tool?▼

Yes. When the Workflow tool is absent, the Skill selects the portable pacer and drives continuous in-session ticks using the same helper scripts and convergence gate, rather than aborting.

Does autoconverge support multiple pull requests at once?▼

Yes. The multi-PR path creates one worktree per PR and either fans out with converge_multi.mjs on the workflow pacer or runs the portable driver once per PR, followed by per-PR teardown.

What happens when Copilot quota or Codex is unavailable?▼

A Copilot quota pre-check maps non-zero exits to a skipped gate with no agent spawned. A genuine codex_down result is recorded as a transparent note and the run advances with the gate bypassed rather than blocking.

Why does autoconverge stop with a user-review blocker?▼

The run stops with blocker user-review when Copilot code-concern findings remain inconclusive after executed-check verification. The user is paged with the findings and review link, and the PR stays a draft until they respond.