Audit, elements-of-style, Assisted-by footer, and
why-not-what guidance already live in describing-changes.
Repeating them here added noise and drift risk.

Assisted-by: Claude Opus 4.6 via pi

diff --git a/ai/claude/skills/commit/SKILL.md b/ai/claude/skills/commit/SKILL.md
index 525b4a00..a89eecef 100644
--- a/ai/claude/skills/commit/SKILL.md
+++ b/ai/claude/skills/commit/SKILL.md
@@ -7,33 +7,16 @@ allowed-tools: Bash(jj diff:*) Bash(jj show:*) Bash(jj log:*)
 
 # Commit Changes
 
-Draft clear, reasoning-focused commit messages using the `describing-changes` skill.
-The `elements-of-style:writing-clearly-and-concisely` skill is required as a sub-skill for clarity.
-
 ## Fileset (optional)
 
 `$ARGUMENTS`
 
 ## Process
 
-1. Check if a fileset was provided: `$ARGUMENTS`
-2. If a fileset is provided:
-   - Run `jj diff $ARGUMENTS` to view the specific changes being committed
-   - Invoke the `describing-changes` skill to draft the commit message based on these specific changes
-3. If no fileset is provided (empty `$ARGUMENTS`):
-   - Run `jj diff` to view all current changes
-   - Invoke the `describing-changes` skill to draft the commit message explaining reasoning
-4. The skill requires `elements-of-style:writing-clearly-and-concisely` for clarity
-5. Audit the message: is every sentence invisible in the diff?
-   - For each sentence, ask: "Does this explain something not visible in the code change?"
-   - If the answer is "no" (sentence just restates what the diff shows), delete it
-   - If all sentences pass the audit, proceed. If any fail, rewrite until they do.
-6. Check if a changelog exists (CHANGELOG.md, CHANGELOG, CHANGES.md, or similar)
-   - If found, add an entry for this change under the appropriate section (usually "Unreleased" or the current version)
-   - The entry should be concise: what changed and why it matters to users
-   - If a fileset is provided, scope the changelog entry to only the changes in that fileset
-7. If a fileset is provided, use `jj commit $ARGUMENTS` to commit only matching files (include the changelog in the fileset if it was updated)
-8. If no fileset is provided (empty `$ARGUMENTS`), use `jj commit` to commit all changes
-9. Include the "Assisted-by" footer with the current model and tool being used
-10. Pass the commit message as a single-quoted string to `-m` (supports multiline)
-11. Verify the commit with `jj show` to confirm only intended changes were committed
+1. Run `jj diff $ARGUMENTS` to view changes being committed
+2. Invoke the `describing-changes` skill to draft the commit message
+3. Check if a changelog exists (CHANGELOG.md, CHANGELOG, CHANGES.md, or similar)
+   - If found, add an entry under the appropriate section
+   - Scope the entry to only the changes in the fileset, if provided
+4. Commit with `jj commit $ARGUMENTS -m '...'` (omit fileset args to commit all; include changelog in fileset if updated)
+5. Verify with `jj show`
diff --git a/ai/claude/skills/jj-describe/SKILL.md b/ai/claude/skills/jj-describe/SKILL.md
index 2b0e39ac..2169ee64 100644
--- a/ai/claude/skills/jj-describe/SKILL.md
+++ b/ai/claude/skills/jj-describe/SKILL.md
@@ -6,22 +6,15 @@ argument-hint: <revision>
 
 # Describe a Change
 
-Draft a reasoning-focused description for a jj revision using the `describing-changes` skill.
-The `elements-of-style:writing-clearly-and-concisely` skill is required as a sub-skill for clarity.
-
 ## Target Revision
 
 `$ARGUMENTS`
 
-**Important:** Completely discard the existing revision description. This command rewrites it entirely.
+**Important:** Completely discard the existing revision description. Start from scratch.
 
 ## Process
 
-1. View the target revision with `jj show -r $ARGUMENTS` to understand the changes
-2. Invoke the `describing-changes` skill to draft a new description explaining reasoning
-   - Do NOT reference or build on the existing message
-   - Start from scratch explaining why this change exists
-   - The skill requires `elements-of-style:writing-clearly-and-concisely` for clarity
-3. Use `jj describe -r $ARGUMENTS` with the drafted message, including the "Assisted-by" footer
-4. Pass the description as a single-quoted string to `-m` (supports multiline)
-5. Verify with `jj show -r $ARGUMENTS` to confirm the message was updated
+1. Run `jj show -r $ARGUMENTS` to view the changes
+2. Invoke the `describing-changes` skill to draft a new description
+3. Apply with `jj describe -r $ARGUMENTS -m '...'`
+4. Verify with `jj show -r $ARGUMENTS`