Menu
Read this skill before making jj commits
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Search the web from the terminal using DuckDuckGo HTML and curl.md for token-efficient results. Use when current web information, docs, issues, or site-restricted search is needed.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Jujutsu (jj) version control reference. Use when working with jj repositories, translating git workflows to jj, or when you need more information about jj commands, revsets, templates, conflicts, bookmarks, or commits.
Cache and refresh remote git repositories under ~/.cache/checkouts/<host>/<org>/<repo> so future references can reuse a local copy. Use this skill when the user points you to a remote git repository as reference or you encountered a remote git repo through other means.
Rust development conventions for formatting, linting, safety comments, and completion checks. Use when writing, editing, reviewing, or testing Rust code.
Based on SOC occupation classification
| name | commit |
| description | Read this skill before making jj commits |
Create a jj commit for the current changes using a concise Conventional Commits-style subject.
<type>(<scope>): <summary>
type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.Signed-off-by).@ already contains the current working tree snapshot.jj commit -m "<subject>" describes the current working-copy commit and creates a new empty working-copy commit on top.jj commit -m "<subject>" <files...> includes only those paths in the committed change and moves remaining changes to the new working-copy commit.jj commit -i -m "<subject>" when you need to interactively choose hunks.jj commit -m $'<subject>\n\n<body>'.jj status and jj diff to understand the current changes (limit to argument-specified files if provided).jj log -n 50 --no-graph -T 'description.first_line() ++ "\n"' to see commonly used scopes.@.jj commit so unrelated changes remain in the new working-copy commit.jj commit -i.jj commit -m "<subject>" (or jj commit -m $'<subject>\n\n<body>' if needed), adding file arguments when the user limited the commit to specific paths.