2.4K skills · sorted by relevance
Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.
Create short commit messages using Conventional Commits, a format that labels the type of change. Emphasize intent, keep the subject concise, and include explanatory text when breaking changes, security fixes, data migrations, or reversions require context.
Generate commit messages from git diffs, staged changes, or written descriptions. Explain the reason and problem behind each change using Conventional Commits, a structured message format, and suggest separate messages for unrelated changes.
Turn Git changes into a clear commit message using Conventional Commits, a format that labels the change type and optional scope. Review repository history to match its conventions, and flag unrelated changes that should be split.
Analyze Git changes, group related files for staging, and create commits using Conventional Commits, a structured message format. Infer the change type and scope from the diff, with optional user overrides for the type, scope, and description.
Use Git changes to generate Conventional Commits messages, a format that labels each change by type, and create commits. The skill suggests splitting unrelated changes and supports explicit scope, type, sign-off, and amendments to the previous commit.
Analyze Git changes and generate Conventional Commits messages, a standard format that labels each change by type. Suggest separate commits for unrelated work, then stage files and commit as needed, using Git alone.
Review Git changes and prepare consistent commit messages using Conventional Commits, a format that labels each change by type and scope. The workflow includes message validation, optional explanatory details, and committing changes through Copilot.
Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, batch splitting of unrelated changes, safe pushes, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.
The English summary is being prepared. Showing the original description.
Write a single-line commit message for Ant Design by reading staged changes, the changes selected for the next commit. It summarizes the full commit intent and follows the style of recent repository commits.
Build workflows that generate changelogs and release notes from commits, pull requests, and releases. Use Keep a Changelog formatting, standardize commit messages with Conventional Commits, and manage version numbers through Semantic Versioning rules.
Save changes made during the current conversation as one Git commit on the current branch. Select specific files, leave unrelated work unstaged, and stop after committing without creating a branch, pushing, or opening a pull request.
Rules, conventions, and constraints for formatting git commit messages and committing at logical boundaries. Trigger when: - Drafting, revising, or validating git commit messages. - Pausing at commit boundaries under the CORE or CONTINUE workflows. - Evaluating whether a changeset should be split into multiple commits. - Prompt contains keywords: commit message, git commit, conventional commits, commit hygiene, commit guidelines, logical boundary, spaghetti diff, atomic commit, commit boundary.
The English summary is being prepared. Showing the original description.
`git commit` / `git commit --amend` を実行する前、または「commit」「amend」「コミット」「コミットして」の一語・短文だけを渡された時点で必ず発火する git コミット実施ルール。理由や差分の説明が一切無くても、ファイル全文を読んでメッセージを組み立てる前に先に参照する。主目的は論理的に独立した修正を都度・適切な粒度でコミットすること。メッセージは Conventional Commits 形式、素材は同梱の決定論スクリプト commit-context.sh が出す staged diff のみ。「コミット分けて」と依頼される、独立した複数修正をまとめるか分けるか判断する、レビューコメント対応をコミットする、rebase / squash / cherry-pick 後のメッセージを整える、`gh pr create` の PR タイトルをコミット流儀へ揃える場面でも参照する。plan モードでのコミット計画の立案は commit-plan スキルの領分。
The English summary is being prepared. Showing the original description.
List Git commits linked to agent work sessions, with branch or repository filters. See each commit’s message, date, linked sessions, and observation counts to review recorded changes alongside their session context.
Write Git commit messages that preserve why changes were made. The skill keeps Conventional Commits subject lines and adds structured body entries for user intent, decisions, rejected alternatives, constraints, and lessons supported by the session context.
Review Git changes and draft commit messages using Conventional Commits, a format that labels the type and scope of a change. Produce concise subjects, explanatory bodies, and issue or breaking change references when needed.
commitlint checks that Git commit messages follow the Conventional Commits format (type(scope): subject) and fails when they do not. Use when a user asks to standardize commit messages, enforce commit conventions with a husky commit-msg hook, lint commits or PR commits in CI, customize rules, or prepare commits for automated changelogs and semantic versioning.
The English summary is being prepared. Showing the original description.
Creates context-aware git commits with smart pre-commit checks, submodule support, and conventional commit message generation. Use when user requests to commit changes, stage and commit, check in code, save work, save changes, push my code, finalize changes, add to git, create commits, run /commit command, or mentions "git commit", "commit message", "conventional commits", "stage files", "git add", or needs help with commits.
The English summary is being prepared. Showing the original description.
Turn Git history into release notes and recommend the next version based on commit types and breaking changes. Check commit formatting, filter changes by package, and generate Markdown or JSON for automated release workflows.
Save working changes as local Git commits with messages that explain the outcome. Follow the project's commit style, select files explicitly, and split clearly separate changes into a few logical commits when appropriate.
Polish Korean commit messages drafted by AI into natural developer language. The skill removes stiff wording and literal translations while preserving the stated changes, commit type, scope, issue numbers, and code identifiers.
Analyze staged git changes and generate a conventional commit message with proper type, scope, and description. Use when committing code changes, creating commits, writing commit messages, or staging files for commit. Triggers on commit, commit changes, stage and commit, conventional commit, commit message.
The English summary is being prepared. Showing the original description.
git commit を作成するときに必ず使用するスキル。ユーザーが「コミットして」「commit して」「変更を記録して」と言ったとき、または変更がまとまり commit すべきタイミングになったときに発火する。コンベンショナルコミット、日本語メッセージ、`--no-gpg-sign`、ブランチ確認、Co-author 付与などプロジェクト固有の必須ルールを含むため、エージェントが内蔵で持つ汎用的な commit 手順より**常にこのスキルを優先**すること。`git commit` を直接呼ぶ前に必ず参照する。
The English summary is being prepared. Showing the original description.