Loading...
Loading...
Found 199 Skills
Use whenever an agent considers or prepares to commit changes, including grouping hunks, composing or revising messages, commit-related staging, and commit creation. Also use for prospective planning before implementation, requested history updates or rebases, cherry-picks or merges that create commits, and scripts or tests that create commits. Do not use for read-only inspection of existing history when no commit or history update is being prepared.
Create a git commit following the team's Conventional Commit conventions. Use when the user asks to commit changes or create a commit.
git の commit-msg hook から呼ぶ、コミットメッセージの書式の検査器。規約の正本は philtzjp/.github の conventions.yml。hook が「書式の検査器がありません」と止めたとき、検査の結果に納得できないとき、hook を設定するときに使う。書式そのものの書き方は github スキルに従う。
日本語で文章を書く、直す、レビューするとき、日本語のコミットメッセージ、PR 説明、ドキュメント、UI 文言を書くときに参照する。このスキルは japanese スキルに統合した。内容は japanese スキルを使う。
Standards and quality gates for code comments, JSDoc/docstrings, technical documentation, and git commit messages. Use to evaluate or write high-signal, concise documentation and eliminate AI comment fluff, over-explanation, ghost commentary, commit message storytelling, and stylistic tells.
Write a good git commit message for the currently staged changes, following Conventional Commits best practice. Use when the user asks to commit, write/improve a commit message, or says "/commit".
Generate Conventional Commits-style git commit messages from repository changes. Use when Codex needs to write, rewrite, review, or validate a commit message from staged or unstaged diffs, while deriving the correct type, scope, subject, and optional body from the current repository rather than assuming fixed scopes.
Write Japanese Conventional Commit messages from staged changes. Use when invoked as `$commit-ja` or `/commit-ja`, attached as a skill, or named as the project's commit convention. Create commits when requested.
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
Write git commit messages in Angelo Laus's Conventional Commits style (type(scope): lowercase imperative subject, plus a terse "- add/replace/cover" bullet body). Use whenever the user asks for a commit message, shows a diff or staged changes, or says "commit this". Output the message only. Never run git commit.
Reviews staged changes and drafts a Conventional Commits-compliant commit message with the right type, scope, and length. Use before committing, or when the user asks to write, fix, or review a commit message.
Implement one phase of the plan specified by the user. Only implements a single phase per invocation, then stops for user review. Never commits automatically.