vibesubinlisted

The vibesubin command and vibe. Runs every code-hygiene specialist in the plugin across a repository in parallel and synthesizes their findings into a single prioritized report. Process skills like `/ship-cycle` and host-specific wrappers like `/codex-fix` are direct-call only and not part of the sweep. Invoke by name (/vibesubin) for a full sweep, or let it route a vague request to the right sub-skill when the operator isn't sure where to start. Read-only by default; fixes apply only after the operator approves items from the report. Two optional output modifiers — `tone=harsh` for direct, no-hedging framing, and `explain=layperson` for plain-language translation (3-dimension box format with "왜 해야 / 왜 중요 / 무엇을 할지" per finding); the two combine. When two specialists give contradictory advice on the same file, the umbrella emits a skill-conflict block (gap / reason / basis per side) instead of silently picking one.
Sordid-cantor687/vibesubin · ★ 0 · Code & Development · score 78

Install: claude install-skill Sordid-cantor687/vibesubin

# /vibesubin `/vibesubin` is two things at once: 1. **A command** — one word that runs every code-hygiene specialist in the pack across the current repo in parallel and returns a single prioritized report. One operator input, one AI output, full repo coverage. Process skills like `/ship-cycle` and host-specific wrappers like `/codex-fix` are direct-call only and not part of the sweep. 2. **A vibe** — a meme-y shorthand for "take a look at my repo with the whole pack and tell me what's up." It's the thing you type when you want the full treatment without having to pick a skill. Both meanings are intentional. The word doubles as a greeting, a command, and a self-description of what the operator is already doing ("vibing with AI on a codebase"). ## ⚠ Incident fast-path — run this **before** anything else Certain phrases mean "something just leaked" and need an immediate response, not a polite routing menu. If the operator's request contains any of these, skip the normal modes and jump directly to `audit-security` in incident mode: - `.env` + any verb like `committed`, `pushed`, `leaked`, `exposed` - `secret leaked`, `token leaked`, `key leaked`, `credential leaked` - `api key committed`, `private key exposed` - `accidentally pushed`, `accidentally committed` - `breach`, `compromised`, `hacked` - `revoke`, `rotate now`, `urgent security` - `pushed my password`, `in git history` For any of these, the response is: 1. **Acknowledge the urgency in one sentence.** "Got it — th