Prefer new commits over squashing in commit skill
Squash only when fixing up the prior commit (bug correction, typo fix).
Refactors, cleanups, and follow-ups get their own commit.

Assisted-by: Claude Opus 4.6 via pi
change muurtxyryuywsplmmurtwoowlnxovnzn
commit 692169273da1b679dd32cfcffc0139bc2b4b90c2
author Alpha Chen <alpha@kejadlen.dev>
date
parent qzykuvpl
diff --git a/ai/claude/skills/jj-commit/SKILL.md b/ai/claude/skills/jj-commit/SKILL.md
index 233058a7..b26d38c4 100644
--- a/ai/claude/skills/jj-commit/SKILL.md
+++ b/ai/claude/skills/jj-commit/SKILL.md
@@ -13,6 +13,12 @@ Execute directly without exploring the codebase first. When asked to
 commit and create a PR, use this skill followed by the `/pr` skill
 unless told otherwise.
 
+**Prefer new commits over squashing.** Use `jj commit` to create a new
+commit by default — even for refactors, cleanups, or small follow-ups.
+Only squash (`jj squash`) when the prior commit specifically needs
+fixing up (e.g., correcting a bug introduced in that commit, fixing a
+typo in code it added). If in doubt, make a new commit.
+
 ## Fileset (optional)
 
 `$ARGUMENTS`