2.5천건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review open commitments in acc and record success or failure with supporting notes. Distinguish self-assessment from owner validation or observed real-world results, and keep commitments open when they are still waiting on an outcome.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize changes into focused branches and commits, write consistent commit messages and pull requests, and run relevant checks before pushing. It also handles dependent pull requests, CI follow-up, and updates that preserve review history.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Save code changes on a new Git branch, select files to commit, and push them to the remote repository. Prepare a descriptive commit message and optionally create a pull request with a summary and test plan.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Commit the current work — runs the quality, consistency and passport gates, branches off main if needed, stages specific files, and writes a commit whose subject states what is now true. Pushes and opens a pull request only with --pr or when the user asks; never merges — a merge happens only when the user explicitly says to merge. Use ONLY on explicit commit intent — user says "commit", "let's commit this", "open a PR", or prefixes with `/commit`. Do NOT auto-invoke on vague end-of-task phrases ("we're done", "wrap up") — those require explicit confirmation first. Never force-pushes or skips hooks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stage files and create a commit in one step with a message matching existing commit style. Use when the user asks to "stage and commit", "add and commit", "commit my changes", or "commit these changes".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
超圧縮コミットメッセージ生成。Conventional Commits形式で件名≤50文字、 「何を」より「なぜ」を重視。日本語・英語両対応。 「コミットメッセージ作って」「/commit」「/genshijin-commit」で起動。 ステージング変更時に自動起動候補。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides Odoo-style commit creation following official Odoo git guidelines. Drafts `[TAG] module: short description` messages, checks whether to amend or create a new commit, stages files explicitly, commits via `git commit -F`, and keeps local history clean before PRs. Auto-invokes for commit-related requests in Odoo repositories and takes priority over generic commit skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The commit-R protocol: a test-driven rewrite of one compartment of Anabasis v2. Commit what is in flight, remove the compartment's tests in an "R:" commit, write them again from a stated hypothesis so the production code fails on purpose, remove the production files in a second "R:" commit, then write the production code again, rewrite the neighbouring functions the old shape bent, and delete what served only it. Use when the operator says "commit R", "commit-R protocol", "remove and rewrite the tests" or "rewrite from scratch", or asks for a test-first pass that looks for a faster, simpler path to the same outcome.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refactor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates commit messages against Conventional Commits specification using programmatic validation. Replaces the git-conventional-commit-messages text file with a tool that provides instant feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ALWAYS use this skill when committing changes. Applies Shipfox agent sequencing for branch checks, scoped validation, and commit creation. Trigger on commit, commit changes, save changes, make a commit, or create commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Escribe un mensaje de Conventional Commits para los cambios en stage y crea el commit, incluyendo la línea de coautoría de atribución de IA. Úsalo cuando la persona pida hacer commit, escribir un mensaje de commit o guardar cambios (p. ej. "haz commit de esto", "escribe un mensaje de commit para estos cambios"). No hace push.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never commits, never touches consent paths. Disjoint from the commit skill (Phase 11 executor): the planner proposes a split; the executor lands one consented commit. Use when a working tree has accumulated heterogeneous changes that should not land as one commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write commit messages under the agent-commits convention - a Conventional Commits fork with no chore catch-all, intent-only type tokens, facts in trailers, and legally-grounded AI provenance (Assisted-by, never Co-authored-by). Use when composing a commit in a repo whose commitlint.config.js extends agent-commits, when deciding between feat/fix/refactor/perf, or when recording AI participation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
実装計画・リファクタリング計画・レビュー対応計画・並列作業のタスク分解など、計画を成果物として書き出すときに必ず参照するコミット計画ルール。plan モードでは ExitPlanMode で plan を提示する前に必須、計画ドキュメントや job-graph のタスク分解・エージェントへの指示文でも同様に適用する。計画成果物にコミット計画セクション（論理的に独立した修正単位での分割と Conventional Commits 形式のメッセージ）が無ければ実装に入らない。「実装計画を立てて」「planを立てて」「実行計画を作って」「リファクタリング計画を立てて」「コミット計画を立てて」「タスクを分解して」と依頼される、複数の独立した修正をまとめるか分けるか計画段階で判断する等の場面では、ユーザーが「コミット」に一切言及していなくても必ず発火する。コミットの実施（素材収集・メッセージ確定・git commit 実行）は commit-flow スキルが担う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.