comment-prototypelisted

# comment-prototype — fast change, validate later For the moments when you want to **see it before paying for it**: a few UI/copy tweaks, an exploratory spike, a "does this even feel right" change. `comment-prototype` optimizes for *time-to-look*, not for merge-readiness — it skips the heavy gate on purpose and hands you something to react to fast. It is the lightweight, local-only prototype path of the `comment-dev` family. The merge-ready paths are `comment-feature` and `comment-bug`; this skill **promotes into them** once the change earns the investment. ## What it deliberately skips (until you promote) - ❌ the **`review-loop`** review gate - ❌ opening a **PR** / driving to merge-ready (`ship`) - ❌ pushing the prototype branch - ❌ the full worklog ceremony (plan, decision log, review rounds) ## What it still does - ✅ a **task branch** off fresh `origin/main` (so the work is promotable, never lost) — a sensible default is `proto/<name>`, or the repo's branch convention (see **Repo config**); never `main`. - ✅ a **lightweight worklog** note so the change is watchable and the context survives into promotion (one short comm: what you're trying + a running list of what changed). Use the first working Comment.io route and its identity; invoke `comment-identity` only for an uncredentialed direct-REST write. For a genuinely throwaway visual check the user can say "no comm" and you skip it. - ✅ a focused affected-test check (typecheck/build + the tests nearest the