Results for “git-commits”

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 format, issue references, and AI attribution.

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

Git workflow automation and guidance for Nick's multi-project workflow, especially repos in ~/Projects/. Use when doing git commits, status checks, branching, merges, rebases, reviewing dirty working trees, cleaning branch flow, or managing multiple repos. Enforce conventional commits and safer git habits.

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

Formats git commits with Sentry-style conventional commit messages, including type, scope, subject, body, and issue references, and enforces branch safety by creating a feature branch when on main or master.

Manages git worktrees and submodules in monorepos, handling branch synchronization, commits, pushes, pulls, and branch switching across multiple repositories.

General GitHub workflow — branching, commits, pull requests, code review, secrets hygiene, submodules, and git worktrees. Use when the user wants to save changes, push to GitHub, open a PR, work with a submodule, set up a worktree, or perform any git/GitHub operation.

Generates a concise bullet-point summary of branch changes for a pull request description, grouping related commits by theme and verifying details against actual files.

Quickly refreshes project state when resuming work by reporting git status, recent commits, environment, memory staleness, pending tasks, and red flags.

Automates project releases with version bumping, multi-language changelog generation, and GitHub Release creation. Supports Node.js, Python, Rust, and generic projects.

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.

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.

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.

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.

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.

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.

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.

Author pull requests with intent-separated commits, blast-radius disclosure, and verification evidence. Load when opening a PR, writing a PR description, separating refactor from feature commits, or summarizing a change set for review. Also triggers on "write the PR", "PR body", "intent-separated commits", "split refactor from feature", "pr summary", or after safe-change cycles complete. Extends git-workflow-and-versioning — does not replace it.

Closes out a working session by updating docs/progress.md, reporting uncommitted and unpushed git work, and listing decisions and open threads. Read-only on git, never commits or pushes.

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.

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.

Collaborates with users to design structured development plans broken into testable commits, with research and clarification steps.

Guides creating small, issue-linked pull requests with conventional branch naming, commit messages, and structured descriptions, plus a review cycle.

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

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.