check
Full repo scan — duplicates / unused / oversized / unfinished work, then a subagent verifies every candidate
hi-vibe first guide — start here when unsure what to use.
> /plugin marketplace add jx-hxxx/hi-vibe > /plugin install hi-vibe@hi-vibe-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
/welcomeContext preview
What this command does when you run it.
hi-vibe first guide — start here when unsure what to use.
description: "hi-vibe first guide — start here when unsure what to use."
Read `${CLAUDE_PLUGIN_ROOT}/skills/docs-keeper/SKILL.md`.
Mode: `welcome` Arguments: $ARGUMENTS
Follow that mode exactly — **keep it short**, in the **user's language**: a 👋 greeting, one line on what hi-vibe is, then two must-haves: (1) if the `.hi-vibe/` directory is absent in this project (that's the init marker), tell the user to run `/hi-vibe:init` — don't be fooled by an existing CLAUDE.md or the user's own handover.md; (2) **paste the real GitHub URL** https://github.com/jx-hxxx/hi-vibe and ask them to read its README.md for details. Do NOT dump the docs table, full command list, or hook internals.
The vibe-coding seatbelt for Claude Code — catches AI coding mistakes · 바이브코딩 안전벨트, AI 코딩 실수를 막는 플러그인
Repo: jx-hxxx/hi-vibe
Full repo scan — duplicates / unused / oversized / unfinished work, then a subagent verifies every candidate
hi-vibe's own health check — actually runs hi-vibe's 6 hook scripts & scanner to catch silent failure. Not Claude Code's built-in /doctor (that one checks your…
Pre-write reuse gate — check if it already exists first, then decide where it goes
Detect language, then install lint/type/cycle guards — always asks first, merges with existing config
Append a session-handover entry to handover.md (so the next session has enough to pick up from)
Install/check the project doc system (CLAUDE.md, MODULE.md, handover.md, CHANGELOG.md)