메뉴
Make a commit in Git with an appropriate commit message for the currently staged changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Help a maintainer adopt and operate Sacho, the opinionated changelog manager that keeps user-facing release notes as one small Markdown fragment per change under changes.d/ and compiles them into CHANGES.md at release time. Use this skill whenever a repository has a sacho.toml, a changes.d/ directory, or a CHANGES.md built from fragments; whenever the user wants to add Sacho to a project, write or edit a changelog entry for a change they just made, cut a release, publish release notes, or wire `sacho check` into CI or a pre-commit hook; whenever forward-porting a bugfix release across maintenance branches or resolving a changelog merge conflict; and whenever `sacho check` or the changelog merge driver reports a problem. Also use it any time the user mentions Sacho, changes.d fragments, or asks how to write a changelog entry for users instead of generating one from commit messages.
Create and publish releases for the Optique project. Use when releasing a new version, creating a patch release, or creating a major/minor release. Handles CHANGES.md updates, version bumping, tagging, and branch management.
Use this skill when writing any code that builds a command-line interface with Optique in TypeScript or JavaScript. Covers the combinatorial parser model, choosing @optique/core vs @optique/run, value parsers, structured messages, optional()/withDefault()/multiple(), subcommands with command() and or(), shell completion, async parsing, the integration packages, and common mistakes to avoid. Trigger whenever the user is parsing command-line arguments, building a CLI, or adding options or subcommands to a tool.
Expert-level JavaScript testing skill focused on writing high-quality tests that find bugs, serve as documentation, and prevent regressions. Advocates for property-based testing with fast-check and protects against indeterministic code in tests. Does not cover black-box e2e testing.
| name | commit |
| description | Make a commit in Git with an appropriate commit message for the currently staged changes. |
| metadata | {"internal":true} |
| allowed-tools | Bash(git *) |
Please make a commit with an appropriate commit message for the currently staged changes.
Don't touch the staged changes, just create the commit.
The first line of the commit message should be a concise summary of the changes (50 characters or less). You shouldn't follow the conventional commits, in other words, just write a normal commit message without any special prefixes.
The second line of the commit message should be blank.
The rest of the commit message should provide more detailed explanations about the changes, wrapped at 72 characters.
If you have some references like issues or pull requests, you can add them in the body of the commit message, usually after a blank line. Issues and pull requests should be referenced as full URLs instead of #numbers, and you can put some verbs like “Fixes” or “Closes” before the URLs. For just references without any verbs, you can just put the URLs in the body.
When running git commit, pass the commit message via a HEREDOC to
preserve newlines correctly. Never use literal \n escape sequences
inside a quoted string, as they will appear as literal characters in
the commit message. For example:
git commit -m "$(cat <<'EOF'
Summary line here
Detailed explanation here.
EOF
)"
Don't put Generated with [Claude Code](https://claude.ai/code), or
Co-authored-by trailers at the end of the commit message. Instead,
use the Assisted-by trailer to indicate that the commit was generated by
an AI assistant, if necessary. The format of the Assisted-by trailer should
be:
Assisted-by: AGENT_NAME:MODEL_VERSION
For example:
Assisted-by: OpenCode:qwen3.6-plus
Assisted-by: Claude Code:claude-sonnet-4-6
Assisted-by: Gemini CLI:gemini-3.1-pro-preview
Assisted-by: Codex:gpt-5.4