Analysis updated 2026-05-18
Install a plan, act, verify harness into an existing project so a coding agent's changes get checked before shipping.
Cherry-pick a single skill, such as adversarial verification, without adopting the whole harness.
Give a coding agent a lightweight standing context and permission allowlist instead of letting it improvise.
| archive228/loopkit | asimovinc/asimov-1 | pyenv/pyenv-virtualenvwrapper | |
|---|---|---|---|
| Stars | 712 | 719 | 678 |
| Language | Shell | Shell | Shell |
| Last pushed | — | — | 2017-08-20 |
| Maintenance | — | — | Dormant |
| Setup difficulty | easy | hard | easy |
| Complexity | 2/5 | 5/5 | 2/5 |
| Audience | developer | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
One-line curl install script drops the harness into an existing project directory.
Loopkit is a drop-in set of files that gives a coding agent, such as Claude Code, Cursor, Codex, or Gemini CLI, a structured way of working: plan, act, then verify. It installs into a project's .claude folder with a single install script and does not run as a background service or daemon. Everything it adds is plain files on disk: settings, hooks, a verifier subagent, a loop runner script, and a library of 49 small skills. Each skill is a short markdown document with a YAML header describing what it does and when it should load. Skills only activate when a task actually triggers them, so the agent is not carrying every possible instruction at once. The skills are grouped into ten tracks covering things like agent behavior, long running multi session projects, debugging, and security review. The core loop the project enforces is plan, act, verify, and then revise if verification fails. Planning skills such as spec first and context budget load before work starts. Action skills for tasks like debugging, testing, refactoring, or git operations load while work happens. A separate verifier subagent, described as adversarial, checks the resulting change afterward, assuming it is broken until proven otherwise, and returns its findings as JSON rather than proposing fixes itself. A project using loopkit ends up with a small standing context file limited to 60 lines, a permissions file that allows safe read only commands while blocking risky ones like force pushes, a hooks folder that reminds the agent of the loop shape when a session starts, an MCP configuration file wired to GitHub and Context7 by default, and a memory file meant to be pruned regularly so it does not accumulate stale notes. The project describes itself as opinionated but not a methodology to learn or a vendor lock in. Since it is plain markdown and shell files under an MIT license, a user can keep only the pieces they want and discard the rest. It is aimed at developers who already use an AI coding agent and want a lightweight, file based structure for keeping that agent's work reviewable and verified rather than free form.
Loopkit is a drop-in .claude harness plus 49 markdown skills that give coding agents like Claude Code or Cursor a plan, act, verify workflow enforced by files on disk.
Mainly Shell. The stack also includes Shell, Markdown, YAML.
MIT license: use, modify, and redistribute freely, including commercially, as long as the copyright notice is kept.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.