unvibelisted

# Unvibe ## Quick start ``` /unvibe # analyze recent git changes /unvibe src/lib/auth.ts # analyze a specific file or function ``` ## Setup 1. Detect the language, build system, and test runner from repo files (`package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, etc.). 2. Do not change files silently. Before creating `.unvibe/` or editing `.gitignore`, ask for explicit approval. 3. If the stack or runner is unclear, pause before Phase 2 and ask whether to make a runnable native exercise or a conceptual exercise. ## Mode detection - **Post-session**: no args → inspect `git diff` and `git diff --staged`; if both are empty, inspect the last commit (`git show --stat --patch HEAD`). - **On-demand**: file/function arg → read that specific code. - **Unclear**: ask "Which file or function do you want to unvibe?" ## Bundled resources - `references/reference.md` — rubrics, priorities, and format adaptations. Consult this when you need the Phase 1 question forms, the difficulty rubric, the Examples-happy-path rule, the reference-grounding rule for external-surface facts, or the per-status notes-body layout. - `assets/templates/` — `readme.md`, `index.md`, `test_python.py`, `test_go.go`, `test_ts.ts`. Read the relevant file, fill the `<TOKENS>`, then `Write` the substituted file to the exercise dir. - `assets/runners/python.sh`, `assets/runners/go.sh`, `assets/runners/ts.sh` — copy the matching one to the exercise dir as `run.sh`, `chmod +x`. For o