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 Gap Closure Loop

by ash1794 in ash1794/vibe-engineering

Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves.

MITAuto-check passedDevelopment

Install Vibe Gap Closure Loop

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

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

GitHub CLI
$ gh skill install ash1794/vibe-engineering vibe-gap-closure-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-gap-closure-loop .claude/skills/vibe-gap-closure-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-gap-closure-loop
GitHub stars
163
Token cost
~1.3k tokens
SKILL.md length
570 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves.

  • Works in 6 steps: Triage into Waves → Dependency Analysis & Streams → Dispatch Streams → …
  • Tasks that involve Technical debt
  • SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Arguments and Autonomy, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vibe Gap Closure Loop is an agent skill from ash1794/vibe-engineering. Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Loops through triage, dependency analysis, parallel fix streams, a test gate, and re-audit until the target is met. Use after a gap analysis, audit, or review produces 10+ findings, or to burn down a large bug or tech-debt backlog.

Its SKILL.md is about 1.3k 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, covering Technical debt. 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 Technical debt

Example prompts

  • “Use the vibe-gap-closure-loop skill to close a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves”
  • “/vibe-gap-closure-loop”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Triage into Waves
  2. Dependency Analysis & Streams
  3. Dispatch Streams
  4. Test Gate
  5. Iteration Summary
  6. Check Target

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

    No scripts in the folder and no shell commands in SKILL.md.

    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 Gap Closure Loop loads about 1.3k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 570 words of instructions outside code blocks.

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

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). 570 words, ~1,303 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-gap-closure-loop/SKILL.md (or your agent's skills folder).
name
vibe-gap-closure-loop
description
Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Loops through triage, dependency analysis, parallel fix streams, a test gate, and re-audit until the target is met. Use after a gap analysis, audit, or review produces 10+ findings, or to burn down a large bug or tech-debt backlog.
user-invocable
true

vibe-gap-closure-loop

When you have 50 findings, don't fix them in random order. Triage them into priority waves, fix each wave in parallel streams where dependencies allow, and don't start the next wave until tests pass.

When to Use This Skill

  • After vibe-gap-analysis produced a gap report
  • After any audit, review, or vibe-spec-sync audit that produced 10+ findings
  • A backlog of 10+ bugs or tech-debt items
  • Production readiness sprints

When NOT to Use This Skill

  • Fewer than 5 findings (just fix them directly)
  • Findings that need architectural redesign (use vibe-research-before-design first)
  • All findings are in one file (a single focused pass is simpler)

Arguments

/vibe-gap-closure-loop [dimensions] [--target N] [--gap-file PATH]
  • dimensions: Which gap-analysis dimensions to close (default: all with open findings)
  • --target: Target score per dimension (default: 95)
  • --gap-file: Path to the findings (default: latest docs/plans/gap-analysis-*.md, or ask)

Autonomy

Follow the harness's permission mode. Under an autonomous or auto-approve mode, run the loop without stopping between phases. Otherwise, confirm the wave plan once before Step 3, then continue. Always stop and ask before destructive operations (migrations on real data, force-pushes, deleting files outside the findings' scope).

Step 1: Triage into Waves

Assign every finding a priority:

  • P0 — Blocker: security vulnerability, data-loss risk, breaks core functionality
  • P1 — High: wrong behavior, significant UX issue, missing critical feature
  • P2 — Medium: incomplete implementation, minor bugs, documentation gaps
  • P3 — Low: polish, optimization (candidates for deferral to the backlog)

Wave 0 = all P0, Wave 1 = P1, and so on. Don't start wave N+1 until wave N passes the test gate.

Step 2: Dependency Analysis & Streams

Within the current wave, build a dependency graph:

  • Security findings block everything else
  • Schema/migration changes block feature work on those tables
  • "Add X to Y" depends on Y existing
  • Test-infrastructure changes block test-dependent findings
  • Trivial fixes have no dependencies, so batch them together

Group into parallel streams (use vibe-parallel-task-decomposition for large waves):

  • 3–7 related findings per stream, sized for one agent session
  • No two streams touch the same files (the main source of integration conflicts)
  • A stream that depends on another stream's output moves to the next iteration
Show full SKILL.md (230 more words)Show less

Step 3: Dispatch Streams

If the harness supports subagents, dispatch one per stream in parallel, ideally in isolated worktrees. Otherwise, run the streams sequentially yourself. Let the subagents inherit the session's model unless the user specified one.

Stream prompt:

You are closing findings for [project].

Stream: [name]
Findings: [IDs with full descriptions]

For each finding:
1. Read the relevant source files
2. Implement the fix described
3. Add or adjust a test that fails before the fix and passes after
4. Run the project's test command

Commit with: fix([area]): close [finding IDs]
Do NOT commit if tests fail. Do NOT weaken or delete existing tests to make them pass.
Return: findings closed, findings not closed (with reason), commit hashes.

Step 4: Test Gate

After all streams return:

  1. Integrate the stream branches (vibe-cherry-pick-integration if they were isolated)
  2. Run the full test suite and linters
  3. Fix failures directly (often interactions between streams)
  4. Commit any remaining fixes

Step 5: Iteration Summary

Write docs/plans/closure/iteration-N-summary.md: streams, findings closed, commit hashes, cumulative progress, remaining open findings, and test results.

Step 6: Check Target

  • Re-audit the target dimensions (vibe-gap-analysis --dim N) or re-check the findings list
  • All targets met → DONE: commit and report
  • Otherwise → next wave or next iteration, back to Step 2

Limits

  • Max iterations: 5 per invocation
  • Max parallel streams: whatever the harness handles well; 3–5 is a sensible default
  • Max findings per stream: 7
  • Escalate: a finding that fails to close after 2 iterations gets flagged for human review, not retried indefinitely

Output Format

Gap Closure: [project]

Findings: X total · Closed: Y · Deferred: Z · Escalated: W

WavePriorityFindingsStatus
0P03Complete
1P112In progress (8/12)
2P225Pending
3P310Deferred to backlog
StreamFindingsCommitsTests after
SecurityC-1, C-2, H-1abc123PASS
Escalated to Human Review
  • [finding] — [why it didn't close]

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

Open the folder on GitHubat commit 8f1d71b

Compare with similar skills

Vibe Gap Closure 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 Gap Closure Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Gap Closure Loop this skillash1794/vibe-engineering163—~1.3kAutomated safety check: PassMIT
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT
Code Simplification for ego-litecitrolabs/ego-lite17k—~1.2kAutomated safety check: PassMIT
Code Refactoring Workflowluongnv89/claude-howto42k—~3.1kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Ponytail Debt LedgerDietrichGebert/ponytail159k—~453Automated safety check: PassMIT

Similar skills

  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Code Simplification for ego-lite

    citrolabs/ego-lite

    Finds and implements evidence-backed simplifications in the ego-lite repository, such as dead code, duplicated state and speculative abstractions, without hiding behavior changes.

    17k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Refactoring Workflow

    luongnv89/claude-howto

    Guides systematic, test-backed refactoring in the style of Martin Fowler, moving through research, planning and small incremental changes with your approval at each phase.

    42k GitHub stars~3.1k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed

  • Ponytail Debt Ledger

    DietrichGebert/ponytail

    Collects every ponytail: comment in a codebase into one debt ledger, flags shortcuts with no upgrade trigger and reports without changing any files.

    159k GitHub stars~453 tokensUpdated today
    DevelopmentAuto-check passed

  • FIXME Resolver

    tailcallhq/forgecode

    Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.

    7.6k GitHub stars~1.1k tokensUpdated today
    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 Gap Closure Loop

What does Vibe Gap Closure Loop do?

Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Vibe Gap Closure Loop is an agent skill from ash1794/vibe-engineering. Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves.

When should I use Vibe Gap Closure Loop?

Vibe Gap Closure Loop fits situations like: tasks that involve Technical debt.

How do I install Vibe Gap Closure Loop in Claude Code?

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

How do I install Vibe Gap Closure Loop in Codex?

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

Can I use Vibe Gap Closure 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-gap-closure-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-gap-closure-loop, .gemini/skills/vibe-gap-closure-loop, .github/skills/vibe-gap-closure-loop and .opencode/skills/vibe-gap-closure-loop in your project.

What does Vibe Gap Closure Loop need to run?

SKILL.md names no scripts, command-line tools or credentials: Vibe Gap Closure Loop is instructions for the agent only.

Does Vibe Gap Closure 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 Gap Closure 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 Gap Closure Loop use?

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

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Gap Closure Loop?

Skills that share tags, products or a category with Vibe Gap Closure Loop: Systematic Code Refactoring (luongnv89/claude-howto, 42k stars), Code Simplification for ego-lite (citrolabs/ego-lite, 17k stars), Code Refactoring Workflow (luongnv89/claude-howto, 42k stars) and Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Gap Closure 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.