Codev CLI
Codev runs a GitHub issue through the SPIR protocol: specification, plan, implementation and review, with parallel builders.
- 298 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Builders work autonomously and by the sample configuration start without confirmation prompts, editing code and creating pull requests.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/codevDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Builders work autonomously and by the sample configuration start without confirmation prompts, editing code and creating pull requests.
This is third-party code. Review the repository files before installing.
What it does
Codev is an operating system for human and agent software development. It turns a GitHub Issue into a tested, reviewed pull request: you write the specification and autonomous AI builders handle the rest. The main SPIR protocol has four phases: Specify (define what to build), Plan (break it into executable phases), Implement (write code and tests) and Review (capture lessons). The project gains a `codev/` folder with specs, plans and reviews, and `AGENTS.md` and `CLAUDE.md` files for the agent. Install and start: `npm install -g @cluesmith/codev`, `codev init`, `codev doctor`. `afx spawn <issue number>` launches a builder in a separate git worktree, `consult` asks several models for a second opinion, and `afx workspace start` opens a web dashboard for several builders in parallel. A VS Code extension is available.
Who it is for. Tech leads and developers who run work through specifications and want several builder agents in parallel.
Good fit when
- A GitHub issue must be taken to a pull request with tests and review.
- Several builders work in parallel, each in its own git worktree.
- A decision is checked with several models through `consult`.
- Lessons from each task are saved to `codev/reviews/` for the next ones.
Not a fit when
- A one-line edit: a full specification cycle is excessive.
- Agents must not be allowed to run commands without confirmations.
- There is no Node.js and no GitHub issues in the project.
Example request
Take GitHub issue 42, write a specification and plan by SPIR and show them to me before implementing.Limitations
The sample configuration launches builders with `claude --dangerously-skip-permissions`, meaning Claude Code with no confirmation prompts: limit rights or use an isolated environment. The Agent Farm dashboard is optional, aimed at macOS and less tested on Linux. For OpenCode the builder is set as `opencode run`, and permissions for edits and bash are enabled in its configuration. The figure of 106 PRs in 14 days comes from the author's own measurements. The last commit dates from November 2026.
How to disable. Stop the dashboard and builders and uninstall the package: `npm uninstall -g @cluesmith/codev`. Delete the `codev/` folder, `AGENTS.md` and `CLAUDE.md` in the project by hand if they are not needed.
FAQ
How do I install Codev?
With `npm install -g @cluesmith/codev`. Then in the project run `codev init`, check the setup with `codev doctor` and optionally start `afx workspace start`.
What does SPIR mean?
Specify, Plan, Implement, Review: a description, a breakdown into phases, implementation with tests and capture of lessons.
How do I run a builder on an issue?
With `afx spawn <issue number>`: the agent starts in a separate git worktree with instructions to implement the assigned specification.
Is the Agent Farm dashboard required?
No. All protocols, including SPIR and TICK, work in any assistant without it. The dashboard is for parallel builders.
Which agents are supported as builders?
Claude Code by default, and OpenCode is supported only as a builder. Cursor and Copilot read the project rules through `AGENTS.md`.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI that gives six coding agents project context, over 80 skills, verification and resumable tasks across sessions
A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
A CLI that keeps the spec, tasks and proof of done in git so Claude, Codex, Grok and Cursor can hand work to each other
Orchestrator skill: from an idea the agent writes requirements and a spec, splits work into tasks, builds the project, checks it
FeatherSpec drives spec-driven development in Claude Code and GitHub Copilot: 13 /sdd commands and a Markdown project memory
VBW
Vibe Better With Claude Code
A Claude Code plugin where a team of agents builds the work and a bash kernel accepts nothing until checks pass.
README in short
Codev stores specs, plans and reviews in the repository itself and gives humans and agents a shared language. The `codev/` structure is customisable per team, and local files take precedence over defaults.