git-lorelisted

# Git Lore Preserve decision context beside code by using Git's native commit trailers. Route commit writing and history queries through one skill. ## Route the Request | Request | Mode | |---|---| | Write or perform a non-trivial commit | Commit mode | | Find constraints, rejected options, directives, verification gaps, or other Lore data in history | Query mode | | Configure Lore rules in project or global agent instructions | Setup mode | Repository instructions remain authoritative. Lore supplements existing commit-message rules; it does not replace Conventional Commits, language rules, or repository-specific formats. ## Commit Mode 1. Inspect the staged diff and the verified work from the current task. If nothing is staged, stop and report it; do not stage files unless the user authorized staging them. Never stage unrelated files. 2. Write the summary and body in the repository's required format. If none exists, use a locale-appropriate summary that names the resulting change: an imperative phrase in English. (or a concise noun phrase in Korean if the user or other rules explicitly want to write in Korean) Add an optional body explaining why; do not assume Conventional Commits. 3. Harvest only decision facts supported by the work. Never invent constraints, rejected options, or tests. 4. Append only useful trailers after a blank line. 5. Re-read the message and remove trailers that merely restate the diff. 6. If the user requested an actual commit, run `git