AI NewsDev toolsAnnouncement

GitHub releases lever, a Copilot plugin that writes feedback loops first

GitHub published lever, a Copilot plugin that turns a vague ask like "the editor feels slow" into a measured loop. The repository has 113 stars four days after its first push.

AI News

Editorial2 min read

LinkedInX
Example of /lever picking a playbook from plain words

Image: GitHub

Why it mattersAn agent that can score its own work can grind on a change for hours alone. The hard part is writing down the score, and lever puts that step first.

An agent that can score its own work can grind on a change for hours alone. Give it a number, a way to measure it and a bar for "better", and it keeps going without you. The hard part is writing those three things down. GitHub says most people skip that step, which is why their agents stall. GitHub's own fix for this is a Copilot plugin called lever, pushed to github/lever on 25 October 2026.

The repository has 113 stars on 29 October, four days after its first push. It is MIT-licensed and written in HTML and shell, the GitHub API shows. It installs through the Copilot plugin marketplace.

What the plugin does

The main command is /lever <what is bugging you>, the README says. A plain-words ask such as "our CI is slow" routes to one of about ten verbs. The verb picks a playbook. A loop on a slow test suite returns a Loop Card: the metric, how to measure it, how noisy it is, and what counts as a win. Nothing is pushed, filed or merged in that run.

Other verbs cover more ground. One writes a brief an agent can run unattended. One runs the same change several ways in parallel against a control. One keeps a stack of pull requests green until they land. One turns a chore into a paused automation. A dial called autonomy, from L0 to L5, decides who merges. The project's branch protection still wins, GitHub says.

Where it came from

The README says the skills come from how some of GitHub's own engineers work day to day. Four examples are named. A run of CI speedups. A five-day crate split from three terminals. Weeks of unattended delivery. The automations that took over the chores. The team read its own sessions for what kept working and tried to make it one command, the README says.

What a reader can take from it

A developer does not need the plugin to copy the pattern. The idea is older than the plugin: write the loop first, give the agent a cheap score, and let it iterate. What lever adds is one place to keep the loop and the dial. A team that already has a measurement for the thing it wants to improve can skip the plugin. A team arguing in Slack about whether the editor "feels" slow has nothing to iterate against. The plugin tries to close that gap.

GitHub says the project is early. Issues and pull requests are open on the repository.

Source

SourceGitHub

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX
Start a project