“commits”的搜索结果

按Conventional Commits格式生成简短的提交消息，说明代码变更意图，并为破坏兼容性的变更、迁移等情况补充正文背景。

• 为代码变更编写提交消息
• 统一提交消息格式
• 记录不兼容变更和迁移步骤

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.

中文简介正在准备中。当前显示英语简介。

• Review recent commits linked to agent sessions
• Filter linked commits by branch
• Review linked commits for a specific repository

读取Git差异和近期提交历史，按Conventional 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.

中文简介正在准备中。当前显示英语简介。

• Automating changelog generation from commits and pull requests
• Standardizing team commit messages
• Setting up GitHub or GitLab release notes

Route Git tasks to a dedicated agent to organize commits, branches, and project history. It supports focused commits, repository commit style detection, and interactive rebasing, which lets you reorganize existing commits.

中文简介正在准备中。当前显示英语简介。

• Split changes into focused commits
• Reorganize commits with interactive rebasing
• Manage Git branches

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.

中文简介正在准备中。当前显示英语简介。

• Committing changes with a structured message
• Grouping related files into a logical commit
• Choosing a change type and scope from a diff

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.

中文简介正在准备中。当前显示英语简介。

• Standardize commit messages across a team
• Summarize changes before committing
• Document breaking changes and issue references

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.

中文简介正在准备中。当前显示英语简介。

• Writing a commit message from staged changes
• Recording why a bug fix was needed
• Splitting unrelated changes into separate commit messages

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.

中文简介正在准备中。当前显示英语简介。

• Recording the purpose behind a feature
• Preserving design decisions and rejected alternatives
• Documenting constraints and implementation lessons

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.

中文简介正在准备中。当前显示英语简介。

• Prepare release notes before publishing a version
• Determine the next version from commit history
• Check commit message formats before merging

Plan commits around complete features, fixes, or documentation changes, keeping related tests and docs together. Split larger work into reviewable units with recorded verification results and clear boundaries for rolling back changes.

中文简介正在准备中。当前显示英语简介。

• Split a feature into reviewable commits
• Keep tests and documentation with related code
• Plan related pull requests for a large change

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.

中文简介正在准备中。当前显示英语简介。

• Generate a commit message from staged changes
• Split unrelated changes into separate commits
• Specify a commit type and scope

Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.

中文简介正在准备中。当前显示英语简介。

• Write commit messages using Conventional Commits
• Organize branches and Pull Request reviews
• Resolve conflicts during merge or rebase

Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining for bug analysis, or conduct empirical studies on software defects. Triggers when users ask to find bug-introducing commits, identify when a bug was introduced, trace bug origins, perform SZZ analysis, or analyze bug-fixing commits.

中文简介正在准备中。当前显示原文说明。

Formats commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.

中文简介正在准备中。当前显示原文说明。

Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.

中文简介正在准备中。当前显示原文说明。

Manage complex Git histories with guidance for reorganizing commits, copying selected changes between branches, and finding bug-introducing commits. It also covers working on multiple branches at once and recovering lost commits through Git's reference history.

中文简介正在准备中。当前显示英语简介。

• Clean up commit history before opening a pull request
• Apply selected commits to another branch
• Find the commit that introduced a bug

Reorganize a branch's commit history into a few logical commits without changing file contents. Create a backup first, propose groups for approval, remove merges from main, and check the resulting history and working tree.

中文简介正在准备中。当前显示英语简介。

• Tidying commit history before a pull request
• Grouping changes by feature, fix, tests, or documentation
• Removing merges from main while preserving file contents

Review changes of 1,000 lines or more by dividing work across files, focused areas, and commits. Combine several review methods, check consistency across subsystems, verify bug fixes, and report validated findings alongside a checklist showing review coverage.

中文简介正在准备中。当前显示英语简介。

• Reviewing feature branches with 1,000 or more changed lines
• Checking a large change before merging
• Finding inconsistencies across commits and subsystems

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.

中文简介正在准备中。当前显示英语简介。

• Generate commit messages from changes
• Split unrelated changes into separate commits
• Specify commit types and scopes

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.

中文简介正在准备中。当前显示原文说明。

Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward touches several steps at once and those fixes need splitting back into per-step commits.

中文简介正在准备中。当前显示原文说明。

帮助团队选择适合开发方式和发布节奏的Git分支策略，统一提交记录与拉取请求说明，并梳理本地历史、合并冲突解决、版本标签和发布管理的操作步骤。

• 为新项目选择分支策略
• 统一提交信息和拉取请求说明
• 提交审查前整理本地历史

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.

中文简介正在准备中。当前显示英语简介。

• Saving completed work as a local commit
• Writing messages that explain the outcome
• Separating unrelated changes into commits