A Claude Code plugin for vibe coding that keeps project docs (CLAUDE.md, MODULE.md, handover.md) up to date, sets up lint and type-check guards, analyzes Python and JavaScript/TypeScript repo structure, and enforces root-cause debugging to catch AI coding mistakes.
Auto-invoked ships a router so the right skill fires automatically as you prompt. No remembering which skill to call.
Normal is the plain upstream plugin, installed as-is. You invoke its skills yourself.
Claude Code
The plugin> /plugin marketplace add jx-hxxx/hi-vibe> /plugin install hi-vibe@hi-vibe-marketplaceAuto-invocation> /plugin marketplace add flowy-sh/flowy-core> /plugin install flowy-core> /plugin install flowy-hi-vibe
Codex
$ npx skills add jx-hxxx/hi-vibe -a codex
Cursor
$ npx skills add jx-hxxx/hi-vibe -a cursor
Gemini CLI
$ npx skills add jx-hxxx/hi-vibe -a gemini-cli
GitHub Copilot
$ copilot plugin marketplace add jx-hxxx/hi-vibe$ copilot plugin install hi-vibe@hi-vibe-marketplace
OpenCode
$ npx skills add jx-hxxx/hi-vibe -a opencode
Windsurf
$ npx skills add jx-hxxx/hi-vibe -a windsurf
🇰🇷 한국어로 읽기 → README.ko.md · 🇬🇧 English below.
A vibe-coding seatbelt that stops Claude Code from rebuilding what already exists, papering over errors, and forgetting yesterday's decisions.
Every command, how it works, the FAQ, and the question you can paste into an AI to check whether it fits your project all live there. This file covers installing and using it, nothing more.
Run these inside Claude Code, in order.
/plugin marketplace add jx-hxxx/hi-vibe
/plugin install hi-vibe@hi-vibe-marketplace
/reload-plugins
Don't skip /reload-plugins. Installing alone does not attach the commands and
hooks to your current session.
In the project folder where you want it:
/hi-vibe:init # turn it on for this project — once
/hi-vibe:doctor # confirm it actually runs — once
/hi-vibe:check # sweep the existing codebase — only when you want it
After that there is nothing to memorise. Build the way you already do, and the review, the records and the search for existing code fire on their own.
Install once globally;
initper project./plugin installdefaults to user scope, so one install makes the/hi-vibe:commands available everywhere. The automatic features (hooks) only run in folders whereinitcreated the.hi-vibe/marker. Projects you never raninitin are left completely alone.
| When | What |
|---|---|
| Before you build | Say "build me X" and it searches for an existing implementation first |
| While Claude writes code | Flags errors swallowed in silence and secrets left in the source |
| Once a feature is done | The conversation doesn't end until it has been reviewed — a checklist plus a second Claude that never wrote the code |
| When comparable before/after numbers appear | Records the command, environment, sample, and result in evidence/METRICS.md |
On compact, /clear, or closing | Leaves the next chat enough to pick up from in handover.md |
| When a new session starts | Reads that back, along with the project's own rules |
handover.md inside the project
(gitignored by default). Anything that looks like a secret is masked; ordinary
sensitive information is not.touch .hi-vibe/optout. To remove it entirely,
rm -rf .hi-vibe .repo-xray — the documents it created stay.gitleaks too./hi-vibe:doctor first. It actually executes the
hooks and the scanner and tells you where it stopped.Stars on GitHub
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraHelps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
@mattpocockGives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
@affaan-mDeveloper tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
@facebookInstall it once and the right skill fires as you prompt, with no slash command to remember. It is listed on Flowy in the Development category. It includes docs-keeper, grounded-answers, guards-setup. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it