commit-triagelisted

# Commit Triage Use this skill at the end of a working session, or any time `git status` has become noisy, to produce **clean grouped commits** while archiving failed experiments and pausing on anything ambiguous. This skill exists because committing after long research sessions is the single most common flashpoint for unwanted autonomous actions — stray Co-Authored-By tags, accidentally committed scratch directories, or failed experiments mixed into a feature commit. The triage step is the guardrail. ## Core rules (non-negotiable) - **NEVER** add `Co-Authored-By: Claude` (or any co-author attribution) to commit messages, unless the user explicitly asks for it. - **NEVER** use `git add .` or `git add -A`. Always stage named paths so nothing sneaks in. - **NEVER** `git push` unless the user explicitly asked. Produce the commit, then stop. - **NEVER** delete files. Move failed experiments into `failure/` with `git mv` so they remain recoverable from git history. - Pause and ask on anything that looks destructive, ambiguous, or unfamiliar (new top-level directories, renames, submodule changes, lock-file bumps, large generated artifacts). ## Inputs to confirm Ask only for what is missing: - target repository (default: current working directory) - whether the user wants a single commit or multiple logical commits - any directories or patterns the user wants to always treat as failure or always skip (e.g. `write/`, `scratch/`, `_gen/`) If the user just says "commit" without