'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

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a commit message for code changes
• Standardizing commit message format
• Documenting breaking changes and migration steps

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

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

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

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

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

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

Manage version control through GitButler’s but CLI. Select files or hunks, meaning sections of a diff, for commits; organize dependent branches, split or combine history, resolve conflicts, and create pull requests using task-specific command workflows.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Commit selected files or sections of a diff
• Split, combine, or reorder commits
• Arrange branches by dependency

Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update documentation after feature releases
• Check documentation gaps before a release
• Review changes since a specific tag

Undo development changes recorded by GSD using Git revert. Select recent commits or target an entire phase or plan, with dependency checks and confirmation before the rollback runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Selecting recent GSD commits to undo
• Reverting all commits for a development phase
• Reverting changes for a specific plan