luan/vibe
skills/vibe/SKILL.md
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'.
$ install --global
skillsauthnpx skillsauth add luan/dot-claude vibeInstall 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 PM5.5s1 file scanned
SKILL.md
- name:
- vibe
- description:
- 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'.
- allowed-tools:
- Bash, Read, Glob, Skill
- argument-hint:
- <prompt> [--dry-run]
- user-invocable:
- true
Vibe
Full pipeline (spec → develop → review → commit) from a single prompt.
Arguments
<prompt>— what to build (required)--no-review— skip review stage--dry-run— spec only, stop before develop
No prompt → tell user: /vibe <what to build>, stop.
Pipeline
Stage numbering [N/M]: M = total stages that will run. Base: 5 (spec, develop, review, commit, report). --no-review → 4. --dry-run → 1.
[1/M] Spec
Output [1/M] Spec.
Skill("spec", args="<prompt> --auto")
Spec runs silently with --auto and returns both spec and plan file paths. Read the plan file path from the output or find via ct plan latest.
Verify the plan file exists and has content. Immediately proceed to develop.
[2/M] Develop
Output [2/M] Develop.
If --dry-run → stop here. Report the plan file path, suggest /develop <path>.
Skill("develop", args="<plan-file-path> --auto")
Verify all workers completed. If some failed, report per-worker status and stop.
Bugfix detection: If the spec mentions "bug", "fix", "regression", or includes reproduction steps — after develop completes, re-run the reproduction scenario to confirm the fix works. If reproduction still fails, report and stop (do not proceed to review with a broken fix).
Immediately proceed to review.
[3/M] Review
Output [3/M] Review.
Skip if --no-review.
Skill("crit")
Fix any critical issues inline. Immediately proceed to commit.
[4/M] Commit
Output [4/M] Commit.
If git diff --stat is empty → skip.
Skill("commit")
[M/M] Report
Output [M/M] Report.
Skill("report")
Generates a post-implementation summary in ~/blueprints/. Runs silently — failure here doesn't block the pipeline.
Finalize
Report: one line per stage (completed / skipped / failed).
Error Handling
If a stage fails with zero progress:
- Report completed stages + failure details
- Suggest:
/<failed-skill> [args]to retry the failed stage
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/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
luan/supervibe
development
VerifiedTrustedCommunity
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'.
4SKILL.mdUpdated Apr 21, 2026