원클릭으로 Manus에서 모든 스킬 실행

시작하기

commit

스타4

포크1

업데이트2026년 5월 6일 21:24

Read this skill before making jj commits

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

onbjerg

onbjerg/dot

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Format

<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.

Notes

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (no Signed-off-by).
Only commit; do NOT push.
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only include those paths in the jj commit unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

jj notes

jj has no separate staging area. The working-copy commit @ 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.
Use jj commit -i -m "<subject>" when you need to interactively choose hunks.
For a body, pass one message containing the subject, blank line, and body, for example jj commit -m $'<subject>\n\n<body>'.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review jj status and jj diff to understand the current changes (limit to argument-specified files if provided).
(Optional) Run jj log -n 50 --no-graph -T 'description.first_line() ++ "\n"' to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Include only the intended files:
- If no files are specified, commit all current changes in @.
- If files are specified, pass those files to jj commit so unrelated changes remain in the new working-copy commit.
- If only some hunks should be included, use jj commit -i.
Run 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.

이 저장소의 다른 Skills

같은 저장소

web-search

onbjerg/dot

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.

2026-05-074

github

onbjerg/dot

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.

2026-05-064

onbjerg/dot

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.

2026-05-064

librarian

onbjerg/dot

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.

2026-05-064

rust

onbjerg/dot

Rust development conventions for formatting, linting, safety comments, and completion checks. Use when writing, editing, reviewing, or testing Rust code.

2026-05-064

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.

Format

<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.

Notes

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (no Signed-off-by).
Only commit; do NOT push.
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only include those paths in the jj commit unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

jj notes

jj has no separate staging area. The working-copy commit @ 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.
Use jj commit -i -m "<subject>" when you need to interactively choose hunks.
For a body, pass one message containing the subject, blank line, and body, for example jj commit -m $'<subject>\n\n<body>'.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review jj status and jj diff to understand the current changes (limit to argument-specified files if provided).
(Optional) Run jj log -n 50 --no-graph -T 'description.first_line() ++ "\n"' to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Include only the intended files:
- If no files are specified, commit all current changes in @.
- If files are specified, pass those files to jj commit so unrelated changes remain in the new working-copy commit.
- If only some hunks should be included, use jj commit -i.
Run 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.