2.4천건 · 관련도순
Write Git commit messages with a summary and body through the Shell tool using single-quoted text with actual newlines. This avoids quoting failures that can put command syntax into the saved commit message.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create concise commit messages from a code diff, a file list, or a description of changes. The skill selects one emoji that matches the change’s purpose, follows gitmoji conventions, and explains the choice without running Git commands.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Stage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the most recent commit, or reviewing staged changes before committing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a conventional commit message by analyzing staged git changes. Use when the user wants to create, write, or generate a git commit message from their current staged diff. Trigger on phrases like "commit", "commit message", "commit msg", "寫 commit", "提交訊息", "generate commit", or when the user has just finished making code changes and wants to commit them. Also trigger when the user runs /commit-message.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a git commit following project conventions. Use when: commit, commit this, make a commit, commit changes, git commit, save changes, commit my work, stage and commit, detailed commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create conventional commit messages for {{engine_name}} projects by analyzing staged changes. Handles engine-specific concerns like companion file pairing, binary assets, and linking the related plan. ALWAYS use this skill when the user asks to commit, save changes, or create a commit. Trigger phrases include "commit", "create commit", "commit this", "save changes", "save my work". Even if the user simply says "commit" or asks you to commit after finishing a task — invoke this skill, do NOT commit manually via git.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Validate and fix Pinot pre-commit checks for modules affected by a change. Use it before a commit or pull request to address check failures in the relevant parts of the project.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Commit local changes to the current Git branch with a message based on the project's conventions. When staged and unstaged changes coexist, choose which to include. The skill does not push changes or create pull requests.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
커밋 직전에 파일을 정리하고 기존 타입 검사와 테스트를 실행하도록 설정합니다. Husky와 lint-staged의 설치부터 설정 파일 작성과 동작 확인까지 다룹니다.
팀에 맞는 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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.