luan/supervibe
skills/supervibe/SKILL.md
Goal-directed autonomous development — reads the spec, breaks it into chunks, runs each as a vibe cycle. Triggers: /supervibe, 'super vibe', 'multi-phase', 'keep going until done'.
$ install --global
skillsauthnpx skillsauth add luan/dot-claude supervibeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 1:09 PM7.6s1 file scanned
SKILL.md
- name:
- supervibe
- description:
- Goal-directed autonomous development — reads the spec, breaks it into chunks, runs each as a vibe cycle. Triggers: /supervibe, 'super vibe', 'multi-phase', 'keep going until done'.
- allowed-tools:
- Bash, Read, Glob, Grep, Skill
- argument-hint:
- <goal> [--max-iterations N]
- user-invocable:
- true
Super Vibe
Break a goal into independent chunks informed by the spec, run each as a vibe cycle. Structured sequence, not a blind retry loop.
Arguments
<goal>— what to build (required)--max-iterations N— hard cap on vibe iterations (default: 5)
Hard Caps
- Max iterations: 5 (override with
--max-iterations) - Per-iteration: each vibe cycle has its own token budget via
--max-budget-usd - Hit any cap → report what was accomplished, what remains, stop.
[1] Spec
Skill("spec", args="<goal> --auto")
Read the spec file. The spec's Architecture Context tells you the scope — what modules, files, and patterns are involved.
[2] Plan Chunks
Read the spec file via ct spec read <path>. Break the goal into 2-5 independent chunks based on the spec's Architecture Context. Each chunk:
- Can be implemented and tested independently
- Has a clear "done" state
- Fits in a single vibe cycle
Write the chunk plan as a simple numbered list. Each entry: one sentence describing what to build.
[3] Execute Chunks
For each chunk, in order:
- Output
[N/M] <chunk description> - Run
Skill("vibe", args="<chunk prompt> --no-review") - After vibe returns, verify:
git log --oneline -5andgit diff --statto confirm progress - If vibe failed with zero progress, record the failure and move to the next chunk (don't retry the same chunk — the approach needs adjusting)
After all chunks complete, run one final review:
Skill("crit")
Skill("commit")
[4] Report
Supervibe: <goal>
Chunks: N/M completed
Spec: <file path>
If max iterations hit before completion, report what remains.
Error Handling
- Chunk fails → record it, continue to next chunk. Failed chunks noted in final report.
- Max iterations hit → stop, report accomplished vs remaining.
- All chunks fail → stop, suggest
/debuggingor manual investigation.
Related Skills
luan/sym
tools
VerifiedTrustedCommunity
Tree-sitter indexed code navigator (ct sym CLI). Use INSTEAD OF Read/Grep/Glob/Bash when exploring existing code, understanding how something works, locating a symbol, tracing the call graph up (impact) or down (trace), finding implementations of an interface, scoping a diff to one symbol, or preparing to edit code you have not read yet. Triggers: 'how does X work', 'explain this class/file/symbol', 'walk me through X', 'what does X do', 'where is X defined', 'who calls X', 'what does X call', 'find implementations of', 'what breaks if I change X', 'outline this file', 'map imports', 'show me this symbol', exploring unfamiliar repo, tracing call graph, scoping diff to a symbol, preparing to edit code I haven't read, about to Read a file over ~500 lines to understand it. Do NOT use for: writing new code from scratch, editing prose or config, running tests, or when a stack trace already names the file and line.
4SKILL.mdUpdated Apr 22, 2026
luan/vibe
development
VerifiedTrustedCommunity
Fully autonomous development workflow from prompt to commit. Chains spec → develop → review → commit. Triggers: /vibe, 'vibe this', 'autonomous workflow', 'just do it all', 'build this end-to-end', 'full pipeline', 'handle everything'.
4SKILL.mdUpdated Apr 21, 2026
luan/vault-sweep
development
VerifiedTrustedCommunity
Comprehensive vault maintenance — cross-references blueprints against codebase state to produce a maintenance plan: archive consumed artifacts, audit docs for staleness, propose new docs for undocumented stable systems. Triggers: 'vault sweep', 'sweep the vault', 'clean up vault', 'vault maintenance', 'what can we archive', 'audit blueprints', 'vault hygiene', 'blueprint cleanup'. Use whenever the user wants a holistic view of vault health rather than archiving a single artifact (that's /archive). Also use when the user asks what's stale, what needs docs, or whether artifacts can be cleaned up.
4SKILL.mdUpdated Apr 21, 2026
luan/test-plan
development
VerifiedTrustedCommunity
Analyze current diff, classify changes by risk, and produce structured manual test plan. Triggers: 'test plan', 'what should I test', 'manual testing', 'verification steps', 'QA checklist'. Exits early for trivial changes. Do NOT use when: writing automated tests — use /develop with TDD. Do NOT use when: reviewing code quality — use /crit instead.
4SKILL.mdUpdated Apr 21, 2026