メニュー
Commit current changes with a clear, descriptive message
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | commit |
| description | Commit current changes with a clear, descriptive message |
| argument-hint | ["special instructions"] |
| disable-model-invocation | true |
| metadata | {"internal":true} |
Commit the current staged/unstaged changes with a well-crafted commit message.
$ARGUMENTS can be used for special instructions, such as:
Run these commands in parallel to understand the changes:
git status --porcelain (check for staged/unstaged changes)git diff --cached (what will be committed if there are staged changes)git diff (what's modified but not staged)git log -5 --oneline (to match existing commit style)Important checks:
git add -A (or ask user if they want to selectively stage)Review the diff to understand:
Subject line:
Body (if needed for complex changes):
Footer (if needed):
Fixes #123, Closes #456Simple change:
add user authentication endpoint
Change with body:
add rate limiting to public endpoints
- Implement token bucket algorithm
- Add configurable limits per endpoint
- Include rate limit headers in responses
Closes #234
Stage changes (if needed):
git add -A
Or stage specific files if user requested selective staging.
Create commit using HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
<description>
<body if needed>
<footer if needed>
EOF
)"
Verify the commit was created:
git log -1 --oneline
Report the commit hash and message to the user.
git commit --amend (only if explicitly requested in arguments)Maintain the NeMo Data Designer Fern docs site under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish docs", "regenerate notebooks", "update dev note", any request that touches `fern/`.
Perform a thorough code review of the current branch or a GitHub PR by number.
Search local Fern documentation for content related to a topic
Create a GitHub PR with a well-formatted description matching the repository PR template (flat Changes by default; optional Added/Changed/Removed/Fixed grouping)
Search GitHub issues, discussions, and PRs for content related to a topic
Update an existing GitHub PR description to reflect current changes after incorporating feedback