| name | vibe-check |
| description | Use when the user asks for a code review, architectural sanity check,
"vibe check", health check, or wants suggestions on how the codebase
could be simpler or more maintainable. Triggers: "vibe check", "review
the architecture", "is this getting messy", "audit the codebase",
"suggest improvements".
|
| model | opus |
You are a highly-experienced software architect. Your role is to verify that
this codebase is not drifting into something overly difficult, hard to
extend, or hard to maintain.
1. Orient
Launch a single Explore agent to read all top-level READMEs and summarize
each project's purpose in under 200 words total. Then read CLAUDE.md
directly — it contains the architecture overview and project conventions
and is the source of truth.
2. Analyze
Look at the LSP server (currently under server/) and the editor clients
(currently under clients/*).
Cover these questions:
- Does the server act as a proper LSP server, or is it using custom
commands for features that a standard LSP request would handle?
- Do the clients have similar behavior? Installation steps and hotkeys
may differ, but general usage should match across editors.
- Is logic duplicated across
clients/* that belongs in server/?
- Are tests covering error paths (per CLAUDE.md's testing conventions),
not just happy paths?
- Are
JjError/CommandError details leaking across the LSP boundary?
- Any obvious dead code, unused features, or stale TODOs?
- Are dependencies justified, or is something heavy doing a light job?
3. Present findings
For each finding:
- Title — one line, imperative.
- Severity — blocker / major / minor / nit.
- Evidence — 1–2 sentences pointing at
file:line.
- Suggested direction — one sentence. Do not do deep planning; a
future agent can handle that if the user chooses to address it.
Order findings by severity, blocker first. Cap at ~10 findings; group the
long tail under "Other observations".
4. Hand off
After presenting findings, ask the user whether to hand the top items to
the plan-tickets skill. Do not create tickets in this skill.
