Results for “git-commits”

Use when creating Git commits.

Creates atomic git commits with terse Conventional Commits messages and pushes them to the remote, splitting changes by concern and avoiding secret files.

Creates git commits following Sentry conventions, including conventional commit format, issue references, and AI attribution.

Git expert for atomic commits, rebasing, and history management

Transforms git diffs and change descriptions into narrative commit messages that explain why a change was made, following Conventional Commits format.

Creates commits following Sentry conventions with conventional commit format and issue references.

Create commits following Sentry conventions with proper format, issue references, and AI attribution.

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

Git discipline — atomic commits, conventional messages, branch strategy, PR review patterns, git archaeology for debugging, and recovery patterns.

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.

Stages and commits changes with quality checks, status review, and a clear message, then shows recent history.

Creates clean, conventional git commits using standard git. Use when the user asks to "commit", "git commit", "create commit", or wants to commit staged or unstaged changes.

Use when splitting a working tree into atomic commits, or when changes need to be distributed across new commits and/or edits to prior commits on the branch. Especially relevant when changes within a single file belong in different commits.

Provides guidelines for writing conventional commit messages and pull request descriptions, including merge strategy and GitHub username verification.

Creates a git commit and pushes to remote. Use -a to amend. Optionally accepts a commit message.

변경된 파일을 기능별로 그룹화하여 커밋 생성

Creates a conventional commit from staged changes, using an optional user-provided subject.

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

Generate conventional commit message suggestions for staged git changes, aligned with the repository's commit style. Use when the user wants a commit message suggestion, asks what to commit, or says "suggest commit".

Creates a git commit and pushes to remote. Use -a to amend. Optionally accepts a commit message.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Crie mensagens de commit seguindo as convenções Sentry. Use ao fazer commit de alterações de código, escrever mensagens de commit ou formatar histórico git. Segue conventional commits com referências de issues específicas do Sentry.

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. Trigg

Generate changelogs from git history and validate conventional commits. Usage: /changelog <generate|lint> [options]

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Terse conventional commits. Trigger: commit, git commit, /ijfw-commit

Project commit helper for simulator-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository.

当用户明确要求“解决当前 merge / rebase / cherry-pick 冲突、提交代码、创建 commit、把改动分批提交并 push、推送当前分支”时使用。进行中的冲突要先识别 Git 操作和双方原始意图，逐 hunk 做语义合并并运行项目检查，再经用户确认继续操作；普通改动要检查敏感信息与异常差异，拆成可运行、可审查、可回滚的原子提交后确认提交和推送。不得自动发起或中止 merge / rebase / cherry-pick，不得强推或随意改写已发布历史。不要用于普通改动尚未完成或验证失败、只想查看 Git 状态，或要创建 PR 的场景。

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Inspect local git state, commit changes, and branch into isolated worktrees for speculative work.