Requirements
rizsotto/Bear
Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping.
Install Vibe Coverage Enforcer
$ npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ash1794/vibe-engineering vibe-coverage-enforcer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-coverage-enforcer .claude/skills/vibe-coverage-enforcer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibe-coverage-enforcer" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-coverage-enforcer into .claude/skills/vibe-coverage-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coverage-enforcer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-coverage-enforcerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ash1794/vibe-engineering vibe-coverage-enforcer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-coverage-enforcer .agents/skills/vibe-coverage-enforcer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-coverage-enforcer" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-coverage-enforcer into .agents/skills/vibe-coverage-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coverage-enforcer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ash1794/vibe-engineering vibe-coverage-enforcer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-coverage-enforcer .cursor/skills/vibe-coverage-enforcer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-coverage-enforcer" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-coverage-enforcer into .cursor/skills/vibe-coverage-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coverage-enforcer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ash1794/vibe-engineering.git --path plugins/vibe-engineering/skills/vibe-coverage-enforcer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ash1794/vibe-engineering vibe-coverage-enforcer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-coverage-enforcer .gemini/skills/vibe-coverage-enforcer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibe-coverage-enforcer" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-coverage-enforcer into .gemini/skills/vibe-coverage-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coverage-enforcer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ash1794/vibe-engineering vibe-coverage-enforcerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-coverage-enforcer .github/skills/vibe-coverage-enforcer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibe-coverage-enforcer" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-coverage-enforcer into .github/skills/vibe-coverage-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coverage-enforcer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ash1794/vibe-engineering vibe-coverage-enforcer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-coverage-enforcer .opencode/skills/vibe-coverage-enforcer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-coverage-enforcer" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-coverage-enforcer into .opencode/skills/vibe-coverage-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coverage-enforcer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibe-coverage-enforcer- GitHub stars
- 163
- Token cost
- ~1.2k tokens
- SKILL.md length
- 482 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping.
- Works in 4 steps: Parse requirements from the spec… → Scan test files for traceability markers → Map: requirement → test function(s) or… → …
- Tasks that involve Test coverage
- SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Three Coverage Dimensions and Steps, plus 1 more section
- Calls go, npm and pytest
What it does
Vibe Coverage Enforcer is an agent skill from ash1794/vibe-engineering. Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test coverage. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.
When your agent uses it
- Tasks that involve Test coverage
Example prompts
- “Use the vibe-coverage-enforcer skill to enforce tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test…”
- “/vibe-coverage-enforcer”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Parse requirements from the spec document — each atomic requirement gets an ID
- Scan test files for traceability markers
- Map: requirement → test function(s) or UNCOVERED
- Report: X/N requirements covered (Y%)
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1d71b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gonpmpytest
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibe Coverage Enforcer loads about 1.2k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 482 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 482 words, ~1,160 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-coverage-enforcer/SKILL.md (or your agent's skills folder).- name
- vibe-coverage-enforcer
- description
- Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
- user-invocable
- true
vibe-coverage-enforcer
Coverage numbers don't guarantee quality, but low coverage guarantees surprise.
When to Use This Skill
- Before claiming a feature is complete
- After writing tests, to verify coverage meets standards
- During periodic coverage health checks
- When deciding "do I need more tests?"
- After
vibe-spec-syncupdates the spec — verify tests still cover requirements
When NOT to Use This Skill
- Prototype/spike code that will be rewritten
- Generated code (API clients, schema types)
- Configuration files
- When the user explicitly says coverage isn't a priority for this task
Three Coverage Dimensions
Dimension 1: Line Coverage (by Tier)
Not all code needs the same coverage:
| Tier | Target | What's Included |
|---|---|---|
| Critical | >=90% | Security, authentication, authorization, payment/billing, data integrity, encryption |
| Business | >=80% | Core business logic, API handlers, state management, validation |
| General | >=70% | Utilities, formatting, UI components, logging |
| Exempt | N/A | Generated code, test helpers, one-time scripts |
Dimension 2: Spec-to-Test Coverage
Which spec requirements have corresponding tests?
- Parse requirements from the spec document — each atomic requirement gets an ID
- Scan test files for traceability markers:
- Comment markers:
# req:[REQ-ID]or// req:[REQ-ID] - Function name patterns:
test_req_[REQ-ID]_*
- Comment markers:
- Map: requirement → test function(s) or UNCOVERED
- Report: X/N requirements covered (Y%)
Dimension 3: Spec-to-Code Coverage
Which spec requirements have corresponding implementations?
- For each requirement, search the codebase for implementing code
- Evidence: Note which file(s) and function(s) implement each requirement
- Map: requirement → implementation location(s) or NOT_IMPLEMENTED
- Report: X/N requirements implemented (Y%)
Steps
Run line coverage for the project:
- Go:
go test -cover ./...orgo test -coverprofile=coverage.out ./... - JS/TS:
npm test -- --coverage - Python:
pytest --cov
- Go:
Classify packages/modules into tiers
Compare actual vs. target for each package (Dimension 1)
If a spec document exists, run Dimensions 2 and 3:
- Find the spec (same logic as
vibe-spec-syncStep 1) - Extract requirements with IDs
- Scan tests for traceability markers
- Map requirements to implementations
- Find the spec (same logic as
Report all dimensions
Show full SKILL.md (174 more words)Show less
Output Format
Coverage Report
Dimension 1: Line Coverage
Overall: X%
| Package/Module | Tier | Actual | Target | Status |
|---|---|---|---|---|
| auth/ | Critical | 92% | 90% | PASS |
| handlers/ | Business | 75% | 80% | FAIL (-5%) |
| utils/ | General | 68% | 70% | FAIL (-2%) |
Dimension 2: Spec-to-Test Coverage
Spec: [path/to/spec.md] Requirements Covered: X/N (Y%)
| REQ ID | Requirement | Test(s) | Status |
|---|---|---|---|
| AUTH-001 | Login requires email + password | test_login_credentials | COVERED |
| AUTH-002 | Lockout after 5 failed attempts | — | UNCOVERED |
| CACHE-001 | Cache TTL is 24 hours | test_req_CACHE001_ttl | COVERED |
Dimension 3: Spec-to-Code Coverage
Requirements Implemented: X/N (Y%)
| REQ ID | Requirement | Implementation | Status |
|---|---|---|---|
| AUTH-001 | Login requires email + password | src/auth.py:login() | IMPLEMENTED |
| AUTH-002 | Lockout after 5 failed attempts | — | NOT IMPLEMENTED |
| CACHE-001 | Cache TTL is 24 hours | src/cache.py:get() | IMPLEMENTED |
Summary
| Dimension | Score | Target | Status |
|---|---|---|---|
| Line Coverage (Critical) | 92% | 90% | PASS |
| Line Coverage (Business) | 75% | 80% | FAIL |
| Line Coverage (General) | 68% | 70% | FAIL |
| Spec-to-Test | 8/12 (67%) | 100% | FAIL |
| Spec-to-Code | 10/12 (83%) | 100% | FAIL |
Action Required
handlers/needs +5% line coverage — suggest testing: [specific untested functions]- AUTH-002 not implemented and not tested — implement first, then test
- 4 requirements lack tests — run
vibe-adversarial-test-generationin spec-driven mode
Suggested Tests
[Specific test skeletons for uncovered requirements, with req:[ID] markers]© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/vibe-engineering/skills/vibe-coverage-enforcer of ash1794/vibe-engineering.
Open the folder on GitHubat commit 8f1d71b
Compare with similar skills
Vibe Coverage Enforcer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibe Coverage Enforcer this skillash1794/vibe-engineering | 163 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Requirementsrizsotto/Bear | 6.5k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Crap Analysisardalis/RiverBooks | 135 | 2 repos | ~3.4k | Automated safety check: Pass | None | |
| Code Coverages3s-project/s3s | 311 | — | ~789 | Automated safety check: Pass | Apache-2.0 | |
| Project Statusbactopia/bactopia | 522 | — | ~787 | Automated safety check: Pass | MIT | |
| Check Coverageldayton/Dippy | 243 | — | ~403 | Automated safety check: Pass | MIT |
Similar skills
Crap Analysis
ardalis/RiverBooks
Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code.
Code Coverage
s3s-project/s3s
Measure and grow the line coverage of the s3s crate. An agent skill from s3s-project/s3s.
Project Status
bactopia/bactopia
Show a live snapshot of the Bactopia project state — component counts, GroovyDoc coverage, nf-test coverage, and structural issues.
Check Coverage
ldayton/Dippy
Ensure comprehensive test coverage for a CLI handler. An agent skill from ldayton/Dippy.
Guarding Destructive Operations
kajisho5/ffmpeg-skill
Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of…
More from ash1794/vibe-engineering
All 33 skills in this repoVibe Concurrent Test Safety
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.
Vibe Fuzz Parser Inputs
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).
Vibe Golden File Testing
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily.
Vibe Parallel Task Decomposition
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized.
Vibe Slop Filter
ash1794/vibe-engineering
Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).
Vibe Spec Sync
ash1794/vibe-engineering
Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.
Related
Categories
Questions about Vibe Coverage Enforcer
What does Vibe Coverage Enforcer do?
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Vibe Coverage Enforcer is an agent skill from ash1794/vibe-engineering. Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping.
When should I use Vibe Coverage Enforcer?
Vibe Coverage Enforcer fits situations like: tasks that involve Test coverage.
How do I install Vibe Coverage Enforcer in Claude Code?
Run `npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-coverage-enforcer in ash1794/vibe-engineering) into .claude/skills/vibe-coverage-enforcer in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Coverage Enforcer in Codex?
Run `npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-coverage-enforcer in ash1794/vibe-engineering) into .agents/skills/vibe-coverage-enforcer in your project. Codex loads it when a task matches its description.
Can I use Vibe Coverage Enforcer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ash1794/vibe-engineering --skill vibe-coverage-enforcer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-coverage-enforcer, .gemini/skills/vibe-coverage-enforcer, .github/skills/vibe-coverage-enforcer and .opencode/skills/vibe-coverage-enforcer in your project.
What does Vibe Coverage Enforcer need to run?
Going by SKILL.md and its folder, Vibe Coverage Enforcer needs the command-line tools its instructions call (go, npm and pytest).
Does Vibe Coverage Enforcer access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vibe Coverage Enforcer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vibe Coverage Enforcer use?
Vibe Coverage Enforcer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe Coverage Enforcer use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vibe Coverage Enforcer?
Skills that share tags, products or a category with Vibe Coverage Enforcer: Requirements (rizsotto/Bear, 6.5k stars), Crap Analysis (ardalis/RiverBooks, 135 stars), Code Coverage (s3s-project/s3s, 311 stars) and Project Status (bactopia/bactopia, 522 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Coverage Enforcer?
ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.