Verification Loop
A six-phase verification gauntlet for any Claude Code session: build, type check, lint, tests with coverage, security grep, diff review, then a PASS/FAIL report.
- What
- A six-phase verification gauntlet for any Claude Code session: build, type check, lint, tests with coverage, security grep, diff review, then a PASS/FAIL report.
- Cost
- Free
- Needs
- Use "Verification Loop" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a language-agnostic verification loop that makes Muse prove the work instead of vibing it. Six phases in order, stopping at the first hard failure. Build first: npm run build, with pipefail so piped output does not mask the exit code. Type check: tsc --noEmit for TypeScript, pyright for Python. Lint: the project's own lint script, ruff for Python. Tests with coverage: test suite run with coverage reporting, 80 percent minimum target, total, passed, failed, and coverage all reported. Security: greps for hardcoded secrets (sk- prefixes, api_key), console.log leftovers, and other low-hanging issues. Diff review: git diff stat and per-file review for unintended changes, missing error handling, and edge cases. The output is a fixed VERIFICATION REPORT template with PASS/FAIL per phase and an overall READY or NOT READY for PR verdict with issues to fix. A continuous mode is documented for long sessions: re-run the fast loop every 15 minutes or after major changes. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: secret greps are heuristics, not a substitute for real secret scanning; the gate is only as strict as the project's own tooling. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Verification Loop" with your Muse. Prerequisites: none to install. Pure guidance; works in any project with build/test tooling. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/verification-loop/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Run the verification loop on my current work" or "Verify before I open this PR." 3. Work through the six phases with Muse, fixing failures before moving on. Ask for the final VERIFICATION REPORT. Tip: for long sessions, ask Muse to re-run the fast loop (build + types + tests) every 15 to 30 minutes. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.