Results for “commit”

Conventional Commits形式でコミットする。Triggers on: '/commit', 'コミットして', 'commit changes'

The English summary is being prepared. Showing the original description.

Conventional Commits 形式で git コミットを作成する。staged 差分から type/scope を推定し、breaking change やシークレット混入 (.env 等) を検出。pre-commit フックを必ず通す (`--no-verify` 不可)。「コミットして」「git commit」「変更を記録して」などで使用。

The English summary is being prepared. Showing the original description.

変更をコミットしてドラフトPRを作成する一連のGit/ghワークフロー。ユーザーが「コミットして」「PR作って」「draft PR」等を求めたときに使用し、status/diff確認・命令形コミット・push・gh pr create --draft（--assignee hodanov）まで実行する。ユーザーの明示リクエストが無くても、実装完了後にcommitやPRが必要になった場面（dev-workflowのcommitフェーズ等）では必ずこれを使う。`git commit` や `gh pr create` を単体でBash直接実行しない。

The English summary is being prepared. Showing the original description.

Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project-specific hook policies — complements them.

The English summary is being prepared. Showing the original description.

Create atomic git commits with terse, exact Conventional Commits messages. Cuts noise, preserves intent. Subject ≤50 chars. Body only when "why" isn't obvious. Use when the user says "commit", "commit this", "/commit", or asks to stage and commit changes.

The English summary is being prepared. Showing the original description.

Create atomic git commits with terse Conventional Commits messages, then push to remote. Subject ≤50 chars, body only when "why" isn't obvious. Never force pushes. Use when the user says "commit and push", "commit & push", "/commit-push", or asks to stage, commit, and push in one flow.

The English summary is being prepared. Showing the original description.

Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.

The English summary is being prepared. Showing the original description.

Generates semantic commit messages following the Conventional Commits specification with proper types, scopes, breaking changes, and footers. Use when users request "write commit message", "conventional commit", "semantic commit", or "format commit".

The English summary is being prepared. Showing the original description.

Organize code changes into focused commits and manageable branches, prepare pull requests, and maintain release versions and changelogs. The skill also covers separate working directories for parallel work and checks before committing.

• Split mixed changes into focused commits
• Prepare branches and pull requests for review
• Separate parallel work with git worktrees

Organize code changes into focused commits that follow the project's existing message style. Clean up branch history with rebase, resolve conflicts, and investigate when particular code changed or who last modified a line.

• Splitting changes into focused commits
• Matching the project's commit message style
• Cleaning up branch history before merging

Draft board and committee meeting minutes using the format of past minutes. Organize agendas, supplied materials, attendance, resolutions, and votes into a draft, with placeholders and a checklist for attorney review.

• Drafting board minutes from an agenda and presentation slides
• Matching committee minutes to an established house format
• Checking attendance, quorum, and voting details before review

Get independent code reviews of uncommitted changes, branch differences, or individual commits using Codex or Antigravity. Receive findings with severity, locations, impact, and suggested corrections, and compare where the two reviewers agree or differ.

• Reviewing uncommitted changes for bugs
• Comparing Codex and Antigravity on the same branch diff
• Reviewing a specific commit for security issues

Review uncommitted changes, commits, branch differences, or pull requests in context. Identify bugs and concrete security weaknesses, explain when each issue occurs and how serious it is, and provide actionable feedback grounded in the surrounding code.

• Reviewing uncommitted changes before a commit
• Checking a specific commit or branch difference
• Reviewing a pull request before merging

Apply the project's rules for commit messages, branch names, and bug fixes. The skill also points agents to bundled documentation and requires regression tests, which check that a fixed bug does not return.

• Write commit messages that follow project conventions
• Choose a branch name for a development task
• Include a regression test with a bug fix

Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.

The English summary is being prepared. Showing the original description.

Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.

The English summary is being prepared. Showing the original description.

Stage files, create a commit, and push in one step. Use when the user asks to "stage commit and push", "add commit and push", "commit and push", or "commit and push my changes".

The English summary is being prepared. Showing the original description.

Stage the relevant git changes and create a commit using this repo's emoji-prefixed conventional commit format. Use when the user asks Codex to commit changes, stage and commit selected files, or draft a concise Chinese commit message from the current diff.

The English summary is being prepared. Showing the original description.

Create well-structured git commits from the current working tree. Use when the user says 'commit', 'save my work', 'let's commit this', 'make a commit', or any variation of wanting to commit code to git.

The English summary is being prepared. Showing the original description.

Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.

The English summary is being prepared. Showing the original description.

Create a verified local Git commit when committing changes is requested. Not for explaining commit history, drafting a message only, or postponing a commit. Applies every commit gate and never implies a push or PR.

The English summary is being prepared. Showing the original description.

Create a verified local Git commit when committing changes is requested. Not for explaining commit history, drafting a message only, or postponing a commit. Applies every commit gate and never implies a push or PR.

The English summary is being prepared. Showing the original description.

Summarize the current Git working tree and create a straightforward non-interactive commit. Use when Codex is asked to quickly commit the current work, commit everything currently changed, prepare a concise commit message from the diff, or avoid extra confirmation and commit splitting unless there is a real safety issue.

The English summary is being prepared. Showing the original description.

Claude adapter for preparing and creating PlainTab git commits with scoped, detailed Conventional Commit messages. Use when the user asks to commit, 提交, stage changes, or use precise Conventional Commit / Google-style commit messages.

The English summary is being prepared. Showing the original description.