Have push skill invoke jj-commit when description missing

Author: sm17p

.cursor/skills/jj-bookmark-push/SKILL.md

@@ -9,7 +9,7 @@ Use jj for version control in this project (not git) when creating branches, upd
 
 ## Rules
 
-- **Never push without a description.** jj rejects pushing revisions with no commit message. Before push, ensure current revision has a description: `jj describe -m "message"` or `jj describe` (editor). If the working copy is a new empty revision, describe it or move the bookmark to a described revision.
+- **Never push without a description.** jj rejects pushing revisions with no commit message. Before push, ensure current revision has a description. If it is missing, apply [jj-commit](.cursor/skills/jj-commit/SKILL.md) to add a proper message, then push. Alternatively move the bookmark to a described rev: `jj bookmark set <name> -r <rev> -B` then push.
 - **Never rewrite pushed commits.** No amend/squash of commits already pushed or on a branch with an open PR; that force-pushes and removes GitHub PR comments. Add a new commit for follow-up changes unless the user explicitly requests a force-push.
 
 ## Workflow
@@ -24,6 +24,6 @@ Bookmarks are branch-like pointers. Set: `jj bookmark set <name>`. Set to a revi
 
 | Symptom | Fix |
 | -------- | --- |
-| "has no description" | `jj describe -m "message"` on current rev, then push again. Or move bookmark to a described rev: `jj bookmark set <name> -r <rev> -B` then push. |
+| "has no description" | Apply [jj-commit](.cursor/skills/jj-commit/SKILL.md) to add a proper message, then push. Or move bookmark to a described rev: `jj bookmark set <name> -r <rev> -B` then push. |
 | "Refusing to move bookmark backwards" | Use `-B`: `jj bookmark set <name> -r <rev> -B`. |
 | Remote bookmark moved / conflict | `jj git fetch`; resolve conflict or set bookmark to desired rev with `-B` if needed, then push. |

.cursor/skills/jj-commit/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: jj-commit
+description: Stages and commits changes in jj (Jujutsu VCS) with a clear, concise commit message. Use when committing changes with jj, setting a revision description, or when the user asks to commit with jj.
+---
+
+# jj commit (describe)
+
+Create a commit for the current changes by setting the revision description. In jj there is no staging area; the working copy is the current revision.
+
+## Steps
+
+1. Run `jj status` to see working-copy state and which files changed.
+2. Run `jj diff` to see changes in the current revision (working copy vs parent). Use `-r @` to restrict to the current rev if needed.
+3. Run `jj log -n 5` to see recent commit style.
+4. Write a commit message and run `jj describe -m "message"`.
+
+If the user provides a message hint (e.g. in the request), use it when writing the message.
+
+To start a new change before describing, run `jj new`; then set the description on that revision.
+
+## Commit message rules
+
+- Use the imperative mood ("Add", "Fix", "Remove", not "Added", "Fixes", "Removed").
+- Be concise: one short sentence, ideally under 50 characters.
+- Do NOT use conventional commit prefixes (no `feat:`, `fix:`, `chore:`, etc.).
+- Do NOT add any `Co-Authored-By` or similar trailers.
+- Focus on **what** changed and **why**, not how.
+- If a second line is needed for context, keep it brief.
+
+## Examples of good messages
+
+- `Prevent discount code from being cleared on edit`
+- `Add integration test for offer code persistence`
+- `Remove unused legacy export helper`
+- `Fix thumbnail missing in upsell insert`
+
+When pushing, use [jj-bookmark-push](.cursor/skills/jj-bookmark-push/SKILL.md); never push without a description.