Claude Code Plugins

Community-maintained marketplace

Feedback

Use this skill when the user asks to commit, save, or persist their code changes to version control and describe current changes.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name commit
description Use this skill when the user asks to commit, save, or persist their code changes to version control and describe current changes.
metadata [object Object]

Please follow the steps below to commit your changes with jj (describe current changes).

Run jj log -n 5 to see working copy changes and all current changes.

For each non-empty change without a description (shows as "(no description set)"):

  1. Run jj diff -r <change_id> --git to view the diff
  2. Read related files if needed to understand the context
  3. Use jj describe -r <change_id> to add a meaningful description

If changes were made during this conversation, use conversation context to write accurate descriptions.

Commit Message Format

In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC:

jj describe -m "$(cat <<'EOF'
Commit message here.
EOF
)"

Message Style

Follow the Conventional Commits specification:

<type>(<scope>): <description>

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Code style changes (formatting, no logic change)
  • refactor: Code refactoring (no feature or fix)
  • test: Adding or updating tests
  • chore: Build process, dependencies, or tooling changes

Examples:

  • feat(cli): add --verbose flag for debug output
  • fix(llm): handle API timeout errors gracefully
  • docs(readme): update installation instructions
  • refactor(core): simplify session state management