New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vibe Quality Loop

by ash1794 in ash1794/vibe-engineering

Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence.

MITAuto-check passedDevelopment

Install Vibe Quality Loop

skills CLI
$ npx skills add ash1794/vibe-engineering --skill vibe-quality-loop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ash1794/vibe-engineering vibe-quality-loop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-quality-loop .claude/skills/vibe-quality-loop && rm -rf skills-src

Use ~/.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/

Facts

Skill name
vibe-quality-loop
GitHub stars
163
Token cost
~681 tokens
SKILL.md length
325 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence.

  • Works in 5 steps: Review the diff — Read the whole diff as… → Run the project's own checks — Use what… → Fix only the issues found. Don't add… → …
  • Development work in your project
  • SKILL.md covers When to Use This Skill, When NOT to Use This Skill, The Loop and Steps, plus 2 more sections
  • Calls go

What it does

Vibe Quality Loop is an agent skill from ash1794/vibe-engineering. Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Use after any non-trivial implementation and before claiming it is done.

Its SKILL.md is about 680 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 Development. 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

  • Development work in your project

Example prompts

  • “/vibe-quality-loop”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Review the diff — Read the whole diff as a reviewer would. If the harness has a built-in review command (for example /code-review in…
  2. Run the project's own checks — Use what the repo defines (Makefile, package.json scripts, CI workflow) rather than guessing
  3. Fix only the issues found. Don't add features while fixing.
  4. Loop back to step 1. Track the iteration count.
  5. Exit when the review is clean and all checks pass. Quote the final check output. Don't paraphrase it.

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:

    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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 Quality Loop loads about 681 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 325 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~681

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). 325 words, ~681 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-quality-loop/SKILL.md (or your agent's skills folder).
name
vibe-quality-loop
description
Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Use after any non-trivial implementation and before claiming it is done.
user-invocable
true

vibe-quality-loop

The quality loop prevents premature "done" declarations. Keep iterating until the review is clean and the tests pass, and show the evidence.

When to Use This Skill

  • After an implementation that touches more than a couple of files or any non-trivial logic
  • After implementing a feature with tests
  • Before creating a commit or PR on completed work

When NOT to Use This Skill

  • Single-line fixes or typo corrections
  • Documentation-only changes (use vibe-doc-quality-gate)
  • When the user says "just get it working, we'll clean up later"

The Loop

Implement → Self-review diff → Run checks ─┬─ clean + green → EXIT
                ↑                           │
                └──────── Fix issues ←──────┘

Steps

  1. Review the diff — Read the whole diff as a reviewer would. If the harness has a built-in review command (for example /code-review in Claude Code or /review in Codex), run it. Otherwise check for:

    • Bugs: wrong conditions, off-by-one errors, unhandled error paths, broken edge cases
    • Leftovers: unused imports and variables, debug output, commented-out code
    • Consistency: does it match the naming and idioms of the surrounding code?
    • Scope: anything not requested (vibe-scope-guard)
    • Test integrity: were any tests weakened to pass? (vibe-anti-rationalization-check)

  2. Run the project's own checks — Use what the repo defines (Makefile, package.json scripts, CI workflow) rather than guessing:

    • Full test suite, not just the tests you wrote
    • Linter, formatter, type checker
    • The race detector for concurrent code where the language has one (e.g., go test -race)

  3. Fix only the issues found. Don't add features while fixing.

  4. Loop back to step 1. Track the iteration count.

  5. Exit when the review is clean and all checks pass. Quote the final check output. Don't paraphrase it.

Stop Conditions

  • After 5 iterations without converging, stop and report what's stuck rather than looping further.
  • A failure that also happens on the base branch is pre-existing. Report it; don't "fix" it silently in this change.

Output Format

Quality Loop: [Feature Name]

Iterations: X · Final status: CLEAN / KNOWN_ISSUES

IterationIssues foundFixed
1[list][list]

Final checks: [command] → [result]

Remaining known issues (if any):

  • [issue deliberately deferred, with justification]

© 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-quality-loop of ash1794/vibe-engineering.

Open the folder on GitHubat commit 8f1d71b

Compare with similar skills

Vibe Quality Loop 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.

Vibe Quality Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Quality Loop this skillash1794/vibe-engineering163—~681Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from ash1794/vibe-engineering

All 33 skills in this repo

  • Vibe Concurrent Test Safety

    ash1794/vibe-engineering

    Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

    163 GitHub stars~665 tokensUpdated yesterday
    Auto-check passed

  • Vibe Fuzz Parser Inputs

    ash1794/vibe-engineering

    Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).

    163 GitHub stars~722 tokensUpdated yesterday
    Auto-check passed

  • Vibe Golden File Testing

    ash1794/vibe-engineering

    Implements snapshot/golden file tests with temporal normalization so tests don't break daily.

    163 GitHub stars~669 tokensUpdated yesterday
    Auto-check passed

  • Vibe Parallel Task Decomposition

    ash1794/vibe-engineering

    Analyzes large tasks for independent subtasks that can be safely parallelized.

    163 GitHub stars~717 tokensUpdated yesterday
    Auto-check passed

  • Vibe Slop Filter

    ash1794/vibe-engineering

    Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).

    163 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Vibe Spec Sync

    ash1794/vibe-engineering

    Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.

    163 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Vibe Quality Loop

What does Vibe Quality Loop do?

Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Vibe Quality Loop is an agent skill from ash1794/vibe-engineering. Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence.

When should I use Vibe Quality Loop?

Vibe Quality Loop fits situations like: development work in your project.

How do I install Vibe Quality Loop in Claude Code?

Run `npx skills add ash1794/vibe-engineering --skill vibe-quality-loop -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-quality-loop in ash1794/vibe-engineering) into .claude/skills/vibe-quality-loop in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Quality Loop in Codex?

Run `npx skills add ash1794/vibe-engineering --skill vibe-quality-loop -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-quality-loop in ash1794/vibe-engineering) into .agents/skills/vibe-quality-loop in your project. Codex loads it when a task matches its description.

Can I use Vibe Quality Loop 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-quality-loop -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-quality-loop, .gemini/skills/vibe-quality-loop, .github/skills/vibe-quality-loop and .opencode/skills/vibe-quality-loop in your project.

What does Vibe Quality Loop need to run?

Going by SKILL.md and its folder, Vibe Quality Loop needs the command-line tools its instructions call (go).

Does Vibe Quality Loop access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vibe Quality Loop 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 Quality Loop use?

Vibe Quality Loop 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 Quality Loop use?

About 681 tokens (SKILL.md is roughly 2.7k 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 Quality Loop?

Skills that share tags, products or a category with Vibe Quality Loop: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Quality Loop?

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.