Loading...
Loading...
Found 162 Skills
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.
Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing commits.
Create one or more Conventional Commits following the spec and push the current branch. Use when the user asks to create commits, write a conventional commit message, commit and push changes, or prepare commits before opening a pull request.
Expert in GitHub and GitLab workflows, branch strategies, CI/CD, and cross-platform Git (Windows, Linux, macOS). Produces clear commit messages; shows progress in terminal/chat with colors and emoticons; asks clarifying questions to avoid errors. Use when working with Git, GitHub, GitLab, pull/merge requests, commits, or when the user asks for commit message help or platform-specific Git guidance.
Guide for using git according to my preferences. Use it when you're asked to commit something.
Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.
Guidance for writing git commit messages that follow the Conventional Commits 1.0.0 specification. Use when preparing commit messages, summarizing code changes for a commit, or validating commit text for compliance.
Review full Git working tree changes and propose one or more safe, reviewable commit messages plus commit ordering. Use when the user asks for "git propose", asks how to split current changes into commits, or wants Conventional Commit messages from staged, unstaged, and untracked changes.
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
Git version control and GitHub CLI workflows for commits, branches, pull requests, and code reviews with professional commit message practices.
Review, organize, and commit pending changes. Split into logical commits, stage carefully, and write clear Conventional Commit messages. Use when the user asks to commit, stage changes, or organize work into commits.