Require consent and review for autosquash

Review corrections can use fixups without treating pending history as
complete. Autosquash needs explicit approval for the affected range,
because permission to create a fixup does not permit a rewrite.
Rewritten commits require signing, verification, checks, and independent
final review before completion.

Issue: 3cdc678

diff --git a/.agents/skills/commit/SKILL.md b/.agents/skills/commit/SKILL.md
index 35c8be887c6f525a1a6f7c85574dc21f6394ccc6..f1ef4896e128e68469aa11ee2f02c33ddf0f58ad 100644 (file)
--- a/.agents/skills/commit/SKILL.md
+++ b/.agents/skills/commit/SKILL.md
@@ -39,6 +39,15 @@ exception does not permit unsigned code or documentation commits.
 
 - Commit often. Split the work into small, coherent, working steps, and
   do not wait for a full feature.
 
 - Commit often. Split the work into small, coherent, working steps, and
   do not wait for a full feature.

+- Use fixup commits for review corrections when the task requires them.
+  Report the corrections and the pending fixups, but do not report the
+  work as complete while `fixup!` or `squash!` commits remain.
+- Before autosquashing, obtain the user's explicit approval to rewrite
+  the affected commit range. Permission to create a fixup does not
+  authorize a history rewrite. If approval is absent, stop and ask.
+- After an approved autosquash, sign and verify each rewritten normal
+  commit, rerun the required checks, and obtain independent review of
+  the final range before reporting completion.

 - Push code only with the user's authorization. A remote does not give
   permission to push.
 - Rebase before an authorized push only when the task permits it. Do not
 - Push code only with the user's authorization. A remote does not give
   permission to push.
 - Rebase before an authorized push only when the task permits it. Do not