Vibesubin banner
subinium subinium

Vibesubin

AI community

Description

AI skills that keep your code honest, your secrets unleaked, and your repo from rotting. Built for people who ship real things with AI. Type /vibesubin and let your assistant do the boring discipline for you.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

vibesubin

A portable skill plugin that teaches your AI assistant to refactor, audit, and deploy your code the way I wish it would by default — and lets you run all of it at once with `/vibesubin`.

It's built for people who ship real things with AI but weren't trained as developers. These are the habits I use when I'm coding with an AI myself, packaged as skills so your assistant can follow them without you having to know every rule.

The same `SKILL.md` files work in **Claude Code**, **Codex CLI**, and **any agent supported by [skills.sh](https://skills.sh)** — Cursor, Copilot, Cline, and others. Write once; every host picks it up.

[한국어](./docs/i18n/README.ko.md) · [中文](./docs/i18n/README.zh.md) · [日本語](./docs/i18n/README.ja.md)


Quick start

Install [Claude Code](https://code.claude.com), then run:

/plugin marketplace add subinium/vibesubin
/plugin install vibesubin@vibesubin

Open a repo. Type `/vibesubin`. Every skill fans out across your code in parallel, read-only, and comes back with a single prioritized report — nothing is modified until you approve items. When you want a skill to actually *do* the work, call it by name (`/refactor-verify`, `/setup-ci`, etc.) and it edits your files directly.

Using Codex CLI, Cursor, Copilot, or Cline? Jump to [Install](#install).


What vibesubin is, and what it isn't

A small bundle of AI skills — `SKILL.md` files — that your agent picks up automatically whenever a request matches. You say what you want in plain words (*"split this file safely"*, *"is anything leaking?"*, *"set up deploy"*) and the right skill runs.

The rule every skill shares: **they don't say *done* until they can show you the evidence.** A refactor is finished because four independent checks confirm nothing was dropped, moved, or mis-wired — not because the AI rewrote the file. A security sweep is a triaged list with file:line, not a vibes-based paragraph.

Not a SaaS (nothing leaves your machine), not a compliance tool (