AgentStack
SKILL verified MIT Self-run

Vibe Quality Loop

skill-ash1794-vibe-engineering-quality-loop · by ash1794

Enforces the Implement→Review→Test→Fix→Loop cycle until work is clean. Use after any non-trivial implementation to prevent "good enough" exits.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-ash1794-vibe-engineering-quality-loop

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Vibe Quality Loop? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

vibe-quality-loop

The quality loop prevents premature "done" declarations. You keep iterating until the work is actually clean.

When to Use This Skill

  • After any implementation that touches more than 3 files
  • After implementing a feature with tests
  • When you've made changes and want to verify quality
  • Before creating a commit on completed work

When NOT to Use This Skill

  • Single-line fixes or typo corrections
  • Documentation-only changes
  • When the user says "just get it working, we'll clean up later"

The Loop

┌─────────────┐
│  Implement   │
└──────┬──────┘
       v
┌─────────────┐
│ Self-Review  │ ← Read your own diff. Would you approve this PR?
└──────┬──────┘
       v
┌─────────────┐
│  Run Tests   │ ← ALL tests, not just the ones you wrote
└──────┬──────┘
       │
       ├── Tests pass + Review clean → EXIT (done!)
       │
       v
┌─────────────┐
│  Fix Issues  │ ← Fix what broke, don't add new features
└──────┬──────┘
       │
       └── Go back to Self-Review

Steps

  1. Self-Review — Read your entire diff. Check for:
  • Unused imports/variables
  • Hardcoded values that should be constants
  • Missing error handling at system boundaries
  • Functions over 50 lines
  • Any TODO without an issue reference
  1. Run Tests — Run the full test suite, not just affected tests:
  • If Go: go test ./... and go test -race ./...
  • If JS/TS: npm test or equivalent
  • If Python: pytest
  • Note any failures
  1. Fix Issues — Address ONLY the issues found. Don't add features.
  1. Loop — Go back to step 1. Track iteration count.
  1. Exit — When tests pass AND review is clean. Report iteration count.

Output Format

Quality Loop: [Feature Name]

Iterations: X Final Status: CLEAN / KNOWN_ISSUES

| Iteration | Issues Found | Issues Fixed | |-----------|-------------|-------------| | 1 | [list] | [list] | | 2 | [list] | [list] |

Remaining Known Issues (if any):

  • [Issue that was deliberately deferred, with justification]

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.