'commit' 검색 결과

팀에 맞는 Git 브랜치 전략을 선택하고 커밋과 풀 리퀘스트 작성 방식을 정리합니다. 이력 정리, 충돌 해결, 버전 태그와 릴리스 관리 절차도 다룹니다.

• 새 프로젝트의 브랜치 전략 선택
• 커밋 메시지와 풀 리퀘스트 설명 통일
• 풀 리퀘스트 전 로컬 이력 정리

Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.

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

• Committing related changes in focused groups
• Reorganizing branch history with rebase or squash
• Tracing when and where code changed

Configure a Claude Code hook that checks shell commands before execution and blocks flags that skip Git checks or commit signing. It helps preserve existing commit quality checks while documenting the guard's limits.

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

• Blocking flags that skip commit checks
• Preventing commands that disable commit signing
• Sharing Claude Code guard settings across a team

Trace a file, function, or line through Git history to the agent session linked to its commit. It presents recorded commit details, session summaries, and important observations to help explain the change.

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

• Investigating why a particular line changed
• Finding the agent session behind a function change
• Checking a file's latest commit and author

Create a Git commit from current changes using the session history to explain their purpose. The skill checks which files belong, stages the intended work, and writes a structured message covering changes, rationale, and validation.

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

• Commit completed work with its rationale
• Draft a commit message from the session history
• Check staged files for unrelated changes

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

Read staged Git changes and suggest a message in Conventional Commits format, a structured way to describe changes. Include a concise subject and relevant details, then request confirmation before creating the commit.

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

• Draft a message for staged changes
• Use a consistent commit message format
• Document the purpose of a change

Set up checks that run before each commit using Husky, lint-staged, and Prettier. Format staged files, run existing type-check and test scripts, then verify and commit the configuration.

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

• Adding automated checks before commits
• Formatting staged files with Prettier
• Running type checks and tests before committing

Start data collection for wallets already registered in Tres Finance. Choose transaction history plus balances or balances alone, select all or specific wallets, and confirm the request before receiving the collection job ID.

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

• Collecting data after registering wallets
• Importing transaction history and current balances
• Refreshing balances for selected wallets

Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.

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

• Committing related changes in focused groups
• Reorganizing branch history with rebase or squash
• Tracing when and where code changed

[omh] Commit message or pull-request body to write for a change: draft it in the repository's own convention, with `Tested:` listing only commands observed to run and everything prepared but not run under `Not-tested:`. Use when the user says: commit-pr-authoring, commit message, commit messages, write the commit message, draft the commit message, commit body, squash message, pr body.

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

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

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

Canonical rules for writing git commits in the Shift codebase. Use whenever the user asks to commit, stage and commit, create a pull request that requires commits, or draft a commit message. Enforces Conventional Commits, release-note quality, concise subjects, and logical commit boundaries.

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

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.

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

Prepare and create PlainTab git commits with scoped Conventional Commit subjects and detailed commit bodies. Use when the user asks to commit, 提交, create a git commit, stage changes, or asks for precise Conventional Commits / Google-style commit messages; especially when the worktree may contain unrelated user changes.

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

Draft commit titles and optional commit bodies using the workspace commit naming convention. Use when the user asks for a commit message, commit text, commit title, or wants commit wording in the format `chore|bugfix|feature - <issue_id(s)> <short description>`.

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

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

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

Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.

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

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

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

Triages an already-dirty Git working tree: breaks down every uncommitted change hunk by hunk, separates deliberate edits from tool-written churn, possibly accidental reversions, misplaced scope, and sensitive content, asks the user about the ambiguous cases, and proposes an ordered set of commits plus a list of hunks to hold back. Use when the user invokes `/pc` or `$pc`, asks what they should commit, wants their uncommitted changes broken down, or wants commits proposed for a dirty working tree or pile of accumulated local modifications. To plan commit boundaries for a change before or while implementing it, use `incremental-commits` instead.

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

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

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

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

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

Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.

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

Generate a professional git commit message from the repo's current diff. Analyzes all staged, unstaged, and untracked changes, categorizes them, and creates the commit directly once the user approves it, then asks before pushing it (paste-safe commands are a fallback). Trigger on: "commit", "write a commit", "commit message", "what changed", "summarize changes", "draft commit", "changelog", or any request to commit, stage, or describe the current diff.

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