Results for “git-commits”

Use when creating Git commits.

Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.

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.

Orchestrates multi-agent project builds with persistent state, parallel execution, and atomic git commits.

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

Git expert for atomic commits, rebasing, and history management

Commits changes, rebases on main, and creates a pull request to finish a development task.

Formats git commits using Sentry conventions with conventional commit types, issue references, and AI attribution, while enforcing branch safety.

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

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

Capabilities

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

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.

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

Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.

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.

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.

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.

Generate clear, descriptive commit messages following conventional commits format. Use when committing code, writing commit messages, or when the user asks for help with git commits.

Create commits following Sentry conventions with proper conventional commit format and issue references, including branch safety checks.

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.

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

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.

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.