How do I install the Commit skill?

Run npx skillmds@latest add openwpm/commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit?

openwpm (@openwpm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit by openwpm — Agent Skill

Name: Commit
Author: openwpm

Commit

Use to create a jj commit AND auto-document the result on the active crosslink issue. Writes a conventional-style message with the issue ref, and adds a `--kind result` comment so the audit trail closes. Trigger whenever the user asks to "commit", "commit changes", "commit and push", or finishes a unit of work in a crosslink-tracked repo.

openwpm 4af35d8 2.6 KB Updated Sep 17, 2026

File contents

Commit — jj commit + crosslink result comment

The user wants to commit their current changes. Create a well-formed commit AND automatically record a result comment on the active crosslink issue.

1. Review changes

Run jj diff --stat to see what has changed in the working copy. jj auto-snapshots the working copy — there is no staging area. If the diff looks right, proceed.

2. Write the commit message

Summarize what changed and why (1-2 sentences)
Follow conventional commit style if the project uses it
Never use jj/Jujutsu terminology in the message (project policy) — use version-control-neutral language.
Optionally include the crosslink issue reference if an active issue exists (e.g. [CL-5]). Note: OpenWPM enforces conventional-commits via a commitlint commit-msg hook, so a leading [CL-…] prefix can fight that gate — keep it out of the type/scope header (e.g. append it to the body) or omit it.

3. Create the commit

jj commit -m "<message>"

Always pass -m — jj opens an editor if no message is given.

4. Auto-document the result on the active crosslink issue

After a successful commit, check if there's an active crosslink session with an active issue:

crosslink session status

If an active issue exists, record the commit as a result comment:

crosslink issue comment <issue-id> "Committed: <first line of commit message> | Files: <shortstat summary>" --kind result

For example:

crosslink issue comment 5 "Committed: Add typed comment support to schema | Files: 14 files changed, 312 insertions(+), 48 deletions(-)" --kind result

If no active session or issue, skip the comment silently.

5. Show summary

Display:

The commit hash and message
Files changed summary
Whether the result was recorded on a crosslink issue

Constraints

Never force-push or rewrite commits without explicit user request.
There is no staging area in jj — do not attempt git add. jj tracks the working copy automatically.
Always record the result comment after a successful commit when an active issue exists.
Always pass -m to jj commit — never let jj open an editor.
If the commit fails (e.g. pre-commit hook), fix the issue and retry — do NOT record a result comment for failed commits.

---name: commitdescription: Use to create a jj commit AND auto-document the result on the active crosslink issue. Writes a conventional-style message with the issue ref, and adds a `--kind result` comment so the audit trail closes. Trigger whenever the user asks to "commit", "commit changes", "commit and push", or finishes a unit of work in a crosslink-tracked repo.---# Commit — jj commit + crosslink result commentThe user wants to commit their current changes. Create a well-formed commit AND automatically record a result comment on the active crosslink issue.## 1. Review changesRun `jj diff --stat` to see what has changed in the working copy. jj auto-snapshots the working copy — there is no staging area. If the diff looks right, proceed.## 2. Write the commit message- Summarize what changed and why (1-2 sentences)- Follow conventional commit style if the project uses it- Never use jj/Jujutsu terminology in the message (project policy) — use version-control-neutral language.- Optionally include the crosslink issue reference if an active issue exists (e.g. `[CL-5]`). Note: OpenWPM enforces conventional-commits via a commitlint `commit-msg` hook, so a leading `[CL-…]` prefix can fight that gate — keep it out of the type/scope header (e.g. append it to the body) or omit it.## 3. Create the commit```bashjj commit -m "<message>"```Always pass `-m` — jj opens an editor if no message is given.## 4. Auto-document the result on the active crosslink issueAfter a successful commit, check if there's an active crosslink session with an active issue:```bashcrosslink session status```If an active issue exists, record the commit as a result comment:```bashcrosslink issue comment <issue-id> "Committed: <first line of commit message> | Files: <shortstat summary>" --kind result```For example:```bashcrosslink issue comment 5 "Committed: Add typed comment support to schema | Files: 14 files changed, 312 insertions(+), 48 deletions(-)" --kind result```If no active session or issue, skip the comment silently.## 5. Show summaryDisplay:- The commit hash and message- Files changed summary- Whether the result was recorded on a crosslink issue## Constraints- Never force-push or rewrite commits without explicit user request.- There is no staging area in jj — do not attempt `git add`. jj tracks the working copy automatically.- Always record the result comment after a successful commit when an active issue exists.- Always pass `-m` to `jj commit` — never let jj open an editor.- If the commit fails (e.g. pre-commit hook), fix the issue and retry — do NOT record a result comment for failed commits.

Frequently asked questions