vibe-engineering
38 engineering discipline skills for Claude Code & OpenAI Codex + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development — not theoretical best practices, but patterns that survived 3 weeks of intensive production development with 205+ test files, 11 agents, and 50+ session observations.
"Vibe coding" meets engineering rigor. Every skill here exists because skipping it caused real pain.
Two commands. Instant engineering discipline.
/plugin marketplace add ash1794/vibe-engineering
/plugin install vibe-engineering@vibe-plugins
Claude automatically discovers and applies the right skill for every task — research before design, quality gates before shipping, structured debugging before guessing, test coverage before claiming "done."
What is this?
A skill collection for Claude Code and OpenAI Codex with 38 skills that enforce engineering discipline across any project, plus a lightweight CLI (vibe-cli) for CI/CD pipelines and automation:
- Research & Decision-Making (5 skills) — Think before building
- Quality Gates & Validation (7 skills) — Catch issues before they ship
- Learning & Knowledge Management (5 skills) — Never solve the same problem twice
- Parallel & Multi-Agent Development (4 skills) — Scale your work safely
- Testing Patterns (5 skills) — Test what matters, not just what's easy
- Deployment & Operations (4 skills) — Ship with confidence
- Gap Analysis & Remediation (2 skills) — Audit and systematically close gaps
- Communication & Process (4 skills) — Stay focused, stay clear
- Meta Skills (2 skills) — Skill discovery and routing
Installation
Claude Code
From inside a Claude Code session:
# 1. Add the marketplace (one-time)
/plugin marketplace add ash1794/vibe-engineering
# 2. Install the plugin
/plugin install vibe-engineering@vibe-plugins
Later, pull updates with /plugin marketplace update vibe-plugins.
Local development (unpackaged, for testing plugin changes):
git clone https://github.com/ash1794/vibe-engineering.git
claude --plugin-dir ./vibe-engineering/plugins/vibe-engineering
All 38 skills are now available in every Claude Code session.
OpenAI Codex
Clone the repo anywhere, then symlink the plugin's skills/ directory into .agents/skills/ so Codex can discover the individual skill folders:
# Clone once, symlink many times
git clone https://github.com/ash1794/vibe-engineering.git ~/src/vibe-engineering
# User-wide (available in all projects)
mkdir -p ~/.agents/skills
ln -s ~/src/vibe-engineering/plugins/vibe-engineering/skills/* ~/.agents/skills/
# Or per-project
mkdir -p .agents/skills
ln -s ~/src/vibe-engineering/plugins/vibe-engineering/skills/* .agents/skills/
Codex discovers skills from .agents/skills/ automatically. Each skill's SKILL.md frontmatter drives implicit matching.
Quick Start
After installation, Claude automatically discovers vibe-engineering skills. The bootstrap skill teaches Claude to check for applicable skills before every action.
Explore available skills interactively:
/vibe-engineering:vibe-help
Invoke any skill directly:
# Claude Code
/vibe-engineering:vibe-quality-loop
/vibe-engineering:vibe-research-before-design
# Codex
$vibe-quality-loop
$vibe-research-before-design
CLI: vibe-cli
The vibe-cli CLI wraps critical skills into CI/CD-friendly commands with proper exit codes and JSON output. No dependencies — pure bash.
Setup
# Make it available system-wide (optional)
ln -s $(pwd)/scripts/vibe-cli /usr/local/bin/vibe-cli
# Or run directly from the repo
./scripts/vibe-cli help
Commands
vibe-cli pre-commit # Scan staged changes for secrets, debug code, disabled tests
vibe-cli coverage # Run test coverage and report against tier targets
vibe-cli spec-drift # Detect spec-code drift from staged changes
vibe-cli decisions # Extract decisions from staged diff
vibe-cli validate # Validate skill files and manifests
vibe-cli hook install # Install as git pre-commit hook
vibe-cli hook uninstall # Remove git pre-commit hook
Exit Codes
| Code | Meaning |
|---|
0 | All checks passed |
1 | Blocking issues (CI should fail) |
2 | Warnings only (non-blocking) |
JSON Output
Every command supports --json for machine-readable output:
