sm17p/jj-commit
.cursor/skills/jj-commit/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add sm17p/amfig jj-commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:14 PM195.9s1 file scanned
SKILL.md
- 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
- Run
jj statusto see working-copy state and which files changed. - Run
jj diffto see changes in the current revision (working copy vs parent). Use-r @to restrict to the current rev if needed. - Run
jj log -n 5to see recent commit style. - 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-Byor 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 editAdd integration test for offer code persistenceRemove unused legacy export helperFix thumbnail missing in upsell insert
When pushing, use jj-bookmark-push; never push without a description.
Related Skills
sm17p/wxt-svelte-extension
tools
VerifiedTrustedCommunity
Provides project context for the amgiflol WXT + Svelte 5 browser extension. Use when adding or editing extension code, adding entrypoints, fixing extension bugs, or when working in src/entrypoints or wxt.config.ts.
43SKILL.mdUpdated Apr 16, 2026
sm17p/skill-hygiene
development
VerifiedTrustedCommunity
Checklist for updating project skills when the codebase or workflow changes. Use when applying the skill-maintenance rule, after dependency upgrades or script/e2e/release/issue-format changes, or when the user asks how to keep skills up to date.
43SKILL.mdUpdated Apr 16, 2026
sm17p/releases-changesets
development
VerifiedTrustedCommunity
Uses changesets for versioning and changelog; avoids manual version bumps; aligns with build/zip and workflow_dispatch. Use when cutting a release, adding a changeset, preparing for publish, or when touching version or changelog.
43SKILL.mdUpdated Apr 16, 2026
sm17p/pr-from-issue
tools
VerifiedTrustedCommunity
Creates a GitHub PR for the current work using GitHub MCP; links to an existing issue with Closes
43SKILL.mdUpdated Apr 16, 2026