vibe-engineering skill
33 engineering-discipline skills for Claude Code, Codex and Gemini CLI plus vibe-cli for CI: review, tests, coverage, deploy, rollback
- 164 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The deploy and branch-integration skills steer the agent into merges, deploys and rollbacks, which change working branches and services
- `vibe-cli hook install` writes a hook into `.git/hooks` and can block commits
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/vibe-engineeringDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The deploy and branch-integration skills steer the agent into merges, deploys and rollbacks, which change working branches and services
- `vibe-cli hook install` writes a hook into `.git/hooks` and can block commits
This is third-party code. Review the repository files before installing.
What it does
vibe-engineering gathers techniques the author distilled from three weeks of intensive development of a multi-agent system and packages them as 33 skills under the Agent Skills standard. The agent picks a fitting skill by its description, and you can also call one by hand, for example `/vibe-engineering:vibe-quality-loop` in Claude Code or `$vibe-quality-loop` in Codex. The skills are grouped by stage. Before design come research into prior solutions and a decision journal. For checking there are acceptance gates with PASS or FAIL against criteria, a loop of review, tests and fixes, a trap for agent self-deception (tuning tests, special-casing, unverified claims of completion) and sync of the spec with the code. Testing has golden files, a scenario matrix, adversarial tests and parser fuzzing. For shipping there are a pre-commit audit, a safe deploy with rollback and a guard against leaks on publication. A separate bash utility, `vibe-cli`, moves part of the checks into CI: `vibe-cli pre-commit` looks for secrets, debug code and disabled tests in the staged changes, `coverage` compares coverage and `spec-drift` catches divergence between spec and code.
Who it is for. Engineers and teams who hand large chunks of work to agents and want checkpoints before anyone says done: review, tests and a spec check.
Good fit when
- The agent declared a task finished and you want to check it against criteria rather than its word
- A test gets in the agent's way and you suspect it is bending the check to fit the result
- Parallel agents finished in different branches and their results have to be merged safely
- CI needs a step that blocks a commit with secrets, debug code and disabled tests
- Decisions made during edits should be recorded and the spec brought in line with the code
Not a fit when
- The task is small and a single edit solves it: the skills' checkpoints add extra steps
- You need skills for the context window, output formatting or a task queue: the author removed them in version 2.0 because current agents manage on their own
- The project has no specs: the skills that sync the spec with code and measure spec-to-test coverage are useless without the document
Example request
Run vibe-acceptance-gate against the task criteria and show PASS or FAIL for each item with evidenceLimitations
The skills grew out of one project, Go with React Native and 11 agents, so some advice is tied to that environment. For Codex and Gemini CLI installation uses symlinks into `~/.agents/skills/`, and when upgrading from 1.x the old links must be removed because skill folders gained the `vibe-` prefix. `vibe-cli` is written in plain bash 3.2 and needs GNU grep for scanning. Without GNU grep on macOS the command stops with an error; install it with `brew install grep`.
How to disable. In Claude Code run `/plugin uninstall vibe-engineering@vibe-plugins`. For Codex and Gemini CLI delete the `vibe-*` symlinks from `~/.agents/skills/`. The commit hook is removed with `./scripts/vibe-cli hook uninstall`.
FAQ
How do I install vibe-engineering in Claude Code?
Run `/plugin marketplace add ash1794/vibe-engineering` and `/plugin install vibe-engineering@vibe-plugins`. Updates come with `/plugin marketplace update vibe-plugins`. All 33 skills are then available in every session.
How do I find the right skill among 33?
Call `vibe-help` (`/vibe-engineering:vibe-help` in Claude Code or `$vibe-help` in Codex). It acts as a router and shows the full catalog. The agent also picks a skill itself from the description.
What does vibe-anti-rationalization-check do?
The skill catches an agent's attempts to dodge a check: bending a test to fit the result, special-casing in code and claims of completion without evidence. Call it before saying the work is done.
What does vibe-cli pre-commit check?
In the Git index it looks for secrets, debug code and disabled tests. Exit code 1 means a block, 2 means warnings only, and `--json` prints the result in machine-readable form.
Is there anything for CI?
Yes, `vibe-cli` can be called in GitHub Actions and GitLab CI, for example `./scripts/vibe-cli pre-commit --json` and `./scripts/vibe-cli coverage --spec docs/spec.md`. `hook install` sets the check up as a commit hook.
Discussion
No questions or reviews yet.
Related
SkillsReviews the git diff and the conversation with the agent: catches bugs and gaps between your request and the agent's result. CLI, skill, GitHub Action
Vercel CLI for testing coding agents on your framework: runs Claude Code, Codex and others and measures the success rate
QA agents, skills and an MCP server: test generation, coverage gaps, flaky tests, security scans and chaos testing
Caliper runs agent tasks with and without your skill, then shows whether the skill helps and how many tokens it costs
A CLI to evaluate and evolve agent skills: declarative YAML cases, runs across engines and structured reports
QA Agent for the GigaCode CLI: 14 roles and 6 skills for testing
QaAgentGigacodeCli
Requirements-based testing in GigaCode: from analysis and autotest review to a conclusion, with duplicate search before a bug is filed in Jira
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| vibe-engineering (this card) | no | 164 | |
| Agent Skills by Addy Osmani | no | 113,521 | 25 engineering skills along the development cycle from spec to release without a separate CI CLI |
| Superpowers | no | 313,096 | defines the agent's development process: clarification, plan, TDD, subagents and review |
| VibeSkills | no | 3,803 | an orchestrator that freezes requirements and picks local skills itself |
README in short
The README states the two install steps, lists what is new in version 2.3 and explains that the set was re-audited against current models, with some skills removed as redundant. It then covers installation for Claude Code and for Codex and Gemini CLI, a quick start, a `vibe-cli` reference, the skill catalog by stage and design principles, and ends with the origin story and a skill template for contributions.