В каталоге 183 730 навыков в 14 категориях.
Create git commits following repository style. Use when user asks to "create a commit", "commit changes", "/commit", or...
Conventional Commits形式でのGitコミット自動化。変更を分析し、適切なコミットメッセージを生成してgit add + git commitを実行する。「/commit」「コミットして」と言った時に使用。
Commit staged changes using Graphite. Checks if on trunk and creates a new branch if needed. Updates PR title and summar...
Stage and commit changes with Conventional Commits format and co-author attribution.
Use when the user wants to commit changes, save work, or create a git commit message.
Commit changes following project quality gates and best practices. Run before creating any git commit.
This skill should be used when the user asks to "commit changes", "push my code", "commit and push", "save my work", or...
Prepare and create git commits in this repository using Conventional Commits; use when the user asks to commit or split...
Generate a commit message and create the commit in one step.
Use this skill when the user wants to create a git commit, stage files, write a commit message, or finalize their work w...
Use when committing code changes. Enforces intentional file selection, conventional commits, and why-focused messages.
Create a conventional commit. Use when the user asks to commit changes.
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit styl...
Create atomic commits from session changes only
Read the uncommitted diff in dynamic-neural-field-composer and print conventional commit message(s) for it, grouped by l...
Use when the user asks to commit, create a git commit, checkpoint changes, save work to git, or write a commit message.
Git commit guidelines. Use when creating, amending, squashing, or rewording git commits, staging files, or writing commi...
Guided git commit with atomic commit analysis and conventional commit format
Создаёт git-коммит в формате Conventional Commits по текущим изменениям. Используй, когда просят закоммитить или сделать...
Commit staged (or explicitly named) changes with a single compact, developer-friendly commit message that states what ch...
Create well-structured git commits from the current working tree. Use when the user says 'commit', 'save my work', 'let'...
Use when the user asks to commit the current changes — groups the diff into atomic conventional commits and updates the...
Use when the user asks to commit changes to git. Generates a commit message from the diff and commits directly by defaul...
Commit the work done in this session, skipping files a parallel session also touched.
Create a commit following repository guidelines with proper versioning and changelog updates.
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or forma...
Inspect the diff and commit with a Conventional Commits subject line. Use for /commit, "commit this", "commit these chan...
Write a Conventional Commits message for the staged changes, show it for review, and commit only after the user approves...
Review the diff, then commit with a message that explains why. Never amends, force-pushes or skips hooks unless asked. U...
Reviews, validates and commits authorized changes, merges the task branch into local dev, pushes dev and arms the stagin...
v1.0.0 — Use when the user asks to commit work that already exists in a dirty worktree: inspect the changes, split that...
Safe git commit workflow that prevents commits to main branch. Use when the user asks to "commit changes", "save changes...
Commit staged changes with an auto-generated bulleted commit message. Run /stage first to stage files.
Create a git commit
Verify, record and commit the current session's work — checks green first, PROGRESS updated, message via -F. Use when th...
変更をGitコミットしてTDDサイクルを完了する。REVIEWの次フェーズ。「コミットして」「commit」で起動。
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry...
Create well-formatted commits with conventional commit messages and emoji
Create semantically correct, granular git commits by analyzing staged and unstaged changes
Stage and commit changes with a conventional commit message. Runs pre-commit checks automatically. Optionally prefixes w...
Commit ONLY the changes this session made, never another agent's work in the same checkout. With a message argument, mak...
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Suppor...
Commit current changes with a clear, descriptive message
Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to crea...
Make a git commit in this repository by driving the real commitizen binary under a pty. Use whenever a commit is asked f...
Use to create a jj commit AND auto-document the result on the active crosslink issue. Writes a conventional-style messag...
Stages, commits, and optionally pushes local changes with a conventional commit message — analyzes diffs, generates the...
Create well-structured git commits following conventional commit format. Use when committing changes, preparing commits,...
커밋 생성 - 변경사항 분석 후 커밋 메시지 자동 생성
Create a git commit with a clear, value-communication message. Use when the user asks to commit/save staged or unstaged...
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or...
This skill should be used when the user asks to "commit changes", "craft a commit message", "stage and commit", "commit...
Stage, commit, push, open a PR, and merge to main. Use ONLY on explicit commit intent — user says "commit", "ship it", "...
Format, test, then commit with a conventional commit message
원자적 커밋 생성
Quick commit with build verification
Create well-formatted git commits following project conventions with emoji, type, and scope
Create a conventional commit with a well-formed message. Use when ready to commit changes.
Create a git commit with well-structured message and push to remote following BetterPortal project standards
Commit all uncommitted changes split into focused, detailed commits grouped by goal (including submodules). Covers .giti...
Crear commits siguiendo Conventional Commits. Analiza cambios y genera mensajes descriptivos.
Create a git commit with proper message format and co-authorship
Create a git commit following project conventions. Enforces PREFIX-#.# prefix, imperative mood, no Co-Authored-By. TRIGG...
Commit the current session's changes only, gateway-inline. Session-isolated (never -A, staged set verified against the s...
Creates project commits — Conventional Commits format, message quality (72 char subject, 80 char body), staged-change ch...
git commit code changes with clear messages
Create atomic git commits with terse, exact Conventional Commits messages. Cuts noise, preserves intent. Subject ≤50 cha...
Conventional commit message formatting. Use when creating git commits to ensure messages follow the project's convention...
Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by...
The recommended way to commit code to the repository
Commit the current changes with quality checks, status review, staged diff inspection, appropriate tests, and a clear co...
Create repository-adaptive checkpoint commits for coherent work, including requests to split changes into commits and pu...
Canonical rules for writing git commits in the Shift codebase. Use whenever the user asks to commit, stage and commit, c...
Create a Conventional Commits-compliant git commit — analyzes staged changes, drafts a message, and confirms before exec...
Run pre-commit validation before committing. Use for automated hooks, Terraform cleanup, or emoji reference. For simple...
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a c...
Generate Conventional Commits-compliant messages (feat/fix/docs/chore) in Korean and English. Use when you need to creat...
Create a git commit with Medox conventions (co-author, conventional type/scope). Invoke manually with /commit — do NOT t...
Review changes and create clean git commits. Use when user types /commit or asks to commit changes. Creates well-structu...
Validated commit — runs quick checks before committing. Use when ready to commit changes.
Commit the current changes as atomic commits, recording risks, tradeoffs, and alternatives considered.
変更内容を確認し、適切なコミットメッセージでgit commitを行う。「コミットして」「変更を保存」「commitして」などのリクエストで使用する。
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits with conventional...
Create git commits in spaces/[project]/ with conventional message format. Use for saving progress with quality checks an...
Use this skill when creating a git commit
Quick commit and push with minimal, clean messages
Analyze unstaged changes and suggest atomic commit groups with messages
Use when user says 'commit', 'save changes', 'wrap up', 'done with changes', or wants to create a git commit. Analyzes s...
Create git commits with user approval and no Claude attribution
Use when making any git commit. Always pass what was wrong before the changes as the argument; when nothing was wrong, p...
Commit changes with well-crafted messages, grouping related files into separate commits
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.
Git commit workflow pipeline: atomic unit identification, commit ordering, quality gates, message validation, and post-c...
Use when the user invokes /commit or asks to commit changes, after a code review has been completed and the changes are...
Guidelines for writing commit messages and PR descriptions
Helps with commits. Use when the user mentions commits, git, version control, committing changes, commit messages, or an...
Create git commits in logical groups for all current changes
Create atomic commits from all unstaged changes
Batch-commit all uncommitted changes grouped by relevance. Use when multiple accumulated changes need committing. Invoke...