[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-105336":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":15,"stars7d":15,"stars30d":15,"stars90d":14,"forks30d":14,"starsTrendScore":16,"compositeScore":17,"rankGlobal":9,"rankLanguage":9,"license":18,"archived":19,"fork":19,"defaultBranch":20,"hasWiki":21,"hasPages":19,"topics":22,"createdAt":9,"pushedAt":9,"updatedAt":23,"readmeContent":24,"aiSummary":9,"trendingCount":14,"starSnapshotCount":14,"syncStatus":25,"lastSyncTime":26,"discoverSource":27},105336,"lever","github\u002Flever","github","Copilot skills for building feedback loops, delegating safely, and moving repeatable work into automations.",null,"HTML",237,5,134,0,47,141,83.03,"MIT License",false,"main",true,[],"2026-11-01 00:14:31","# lever\n\n**Feedback loops for coding agents.** A Copilot plugin.\n\n![\u002Flever \u003Cverb> \u003Cyour words>: the verb picks the playbook, the rest is you talking normally](docs\u002Fexamples\u002Ftry.png)\n\n```bash\ncopilot plugin marketplace add github\u002Flever\ncopilot plugin install lever@lever\n```\n\nIn the Copilot app, open these links. Each one asks you to confirm, then opens a pre-filled form:\n\n1. [Add the marketplace](ghapp:\u002F\u002Fplugins\u002Fmarketplace\u002Fadd?source=github%2Flever) (`github\u002Flever`)\n2. [Install the plugin](ghapp:\u002F\u002Fplugins\u002Finstall?source=lever%40lever) (`lever@lever`)\n\nOr do it by hand: **Customize → + Add → Marketplace** with `github\u002Flever`, then **+ Add → Plugin** with `lever@lever`.\n\nStart a new session and try one that only reads:\n\n```text\n\u002Flever loop our test suite feels slow. just the card, don't change anything\n```\n\nYou get a Loop Card back: the metric, how to measure it, how noisy it is, and what counts as a win. Nothing gets pushed, filed or merged.\n\n## Why\n\nAgents get really good once they can check their own work. Give one a number, a way to measure it and a bar for \"better\", and it'll grind on that for hours without you. Without that, you're the loop: pasting screenshots, eyeballing scroll jank, hitting rerun on CI at midnight.\n\nSetting up the loop is the hard part. What do you measure? How noisy is it? What's a real win and what's a lucky run? When do you stop? Most people skip it, which is fair, because it's annoying. lever asks you those questions, writes the answers down, and then lets agents iterate against it.\n\nIt comes from how some of the most AI-forward engineers at GitHub work day to day: CI speedups, a five-day crate split run from three terminals, weeks of [unattended delivery](https:\u002F\u002Fgist.github.com\u002FEvanBoyle\u002F8c1a97f682d92dab8c09d0e1ea73f4a0), and the automations that took over the chores. We mined our own sessions for what kept working, then put most of the effort into making it one command. Same workflow, no PhD required.\n\n## What it looks like\n\n![\u002Flever routes a plain-words ask to the right verb](docs\u002Fexamples\u002Flever.png)\n\n![\u002Flever loop turns \"it feels slow\" into a Loop Card](docs\u002Fexamples\u002Floop.png)\n\n![\u002Flever autonomy shows and sets your dial](docs\u002Fexamples\u002Fautonomy.png)\n\nMore in the **[examples gallery](docs\u002Fexamples.md)**: experiment arms, a brief, the three-terminal refactor, the PR shepherd, cross-model review, an automation, and the verbs that tune lever to you.\n\n\u003Cdetails>\u003Csummary>Copy-pasteable examples\u003C\u002Fsummary>\n\n```text\n\u002Flever our CI is slow and I'm tired of hitting rerun\n\u002Flever loop the editor feels janky when I scroll big files\n\u002Flever arms try the 6 ideas on the card\n\u002Flever brief add offline mode to the editor. ship it by tomorrow\n\u002Flever refactor src\u002Fcore is 400k lines. cut it in half\n\u002Flever shepherd keep my stack green till it lands\n\u002Flever review this PR\n\u002Flever automate make the stack shepherd an automation for this repo\n\u002Flever mirror last 30 days\n\u002Flever steer push immediately, then verify\n\u002Flever autonomy agents can merge docs PRs in this repo, nothing else\n```\n\n\u003C\u002Fdetails>\n\n## Commands\n\n```text\n\u002Flever \u003Cwhat's bugging you>      not sure? describe it. lever picks the verb.\n\nBUILD   make something new\n  brief \u003Cask>                    turn ~20 words into a brief an agent can run unattended\n  deliver [brief|issues]         run lanes in parallel and land the work\n  refactor \u003Cscope> \u003Cgoal>        huge mechanical change: producer, packager, shepherd\n  backlog                        keep enough ready issues in the pool\n  shepherd [pr|stack]            keep PRs green until they land\n  land [prs]                     merge plan for a stack or a batch\n  status                         progress you never have to ask for\n\nLOOP    make something measurably better\n  loop \u003Cproblem>                 find the feedback loop first: a Loop Card\n  arms [ideas]                   one agent per idea, against a control\n  review [pr|plan]               several models, blind; only agreed findings\n\nRUN     make it happen without you\n  automate \u003Ctask>                turn a chore into a paused Copilot Automation\n  health                         why did it stall? one fix, or \"no change\"\n\nYOU     tune lever to how you work\n  mirror [30d]                   a scorecard of how you prompt, from your sessions\n  steer \u003Ccorrection>             say it once, never again\n  autonomy [L0-L5|\u003Cwords>]       who merges. see or set your dial\n  spend [standard|high|max]      how much model to throw at it\n  setup                          first run: set your dials\n  help [verb]                    this list, or one verb in detail\n```\n\nEach verb is a skill in [`skills\u002F`](skills\u002F). The `\u002F` menu shows only `\u002Flever`. Skills that only read and advise, like `loop`, can still load on their own when your ask fits. Anything that pushes, files, opens PRs or schedules runs waits for `\u002Flever \u003Cverb>` or an explicit ask.\n\n## Your dials\n\n- **[Autonomy](docs\u002Fautonomy.md)**, L0 to L5: who merges. L0 only proposes. L2 gets PRs green and you merge. L5 lands, releases and watches. It's your setting, saved in `~\u002F.copilot\u002Flever.yml`, and your repo's branch protection still wins. Start at L2 and turn it up as you trust it.\n- **[Spend](docs\u002Fspend.md)**, `standard` · `high` · `max`: model tier, parallel lanes, review depth and how often things run. A repo can cap it in `.github\u002Flever.yml`.\n\n`\u002Flever setup` asks three questions and writes both ([example](config\u002Fpersonal.example.yml)). For a team, copy [`config\u002Fautonomy.example.yml`](config\u002Fautonomy.example.yml) to `.github\u002Flever.yml`.\n\nWork lever starts is tracked as an issue assigned to you with the [`lever` label](docs\u002Ftracking.md), so `\u002Flever status` can list everything in flight, needs-you first.\n\n## Other ways to install\n\n**Per repo**, so the Copilot coding agent in the cloud gets the skills too:\n\n```bash\nmkdir -p .github\u002Fskills\ncp -r path\u002Fto\u002Flever\u002Fskills\u002F* .github\u002Fskills\u002F\ncp -r path\u002Fto\u002Flever\u002F{docs,templates,config,automations} .github\u002F\n```\n\nSkills link to `..\u002F..\u002Fdocs\u002F...`, so those four folders have to sit next to `skills\u002F`.\n\n**Hacking on lever:** clone it and run `copilot plugin marketplace add .\u002Flever`, then `copilot plugin install lever@lever`. It loads straight from your checkout, so edits show up in your next session.\n\n**Automations:** the recipes in [`automations\u002F`](automations\u002F) install through the GitHub MCP server with `\u002Flever automate`. Each one starts paused, dry-runs on past events, and only then gets turned on. The Copilot app has the automation tools built in; in Copilot CLI, start with `copilot --enable-all-github-mcp-tools`.\n\n## Make it yours\n\nThese skills fit how we work. Yours will be different. `\u002Flever mirror` reads your own session history and shows you what you keep repeating, and `\u002Flever steer` turns those repeated corrections into rules that stick. Fork it and bend it.\n\n## Status\n\nEarly. Issues and PRs welcome.\n\n## License\n\nMIT. See [LICENSE](LICENSE).\n",2,"2026-10-31 04:26:29","CREATED_QUERY"]