Loading...
Loading...
Found 156 Skills
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
Designs git workflows covering branching strategies, trunk-based development, stacked changes, conventional commits, CI/CD pipelines, and repository hygiene. Use when setting up branching models, writing commit messages, configuring GitHub Actions, managing stacked PRs, cleaning stale branches, creating issue templates, or recovering lost commits.
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.
Cut a release — detect versioning context, generate a changelog from conventional commits, bump versions, and create a git tag. Use when the user says "release", "cut a release", "tag a release", "bump the version", "create a changelog", "ship a version", "publish", or any variation of shipping/publishing a version. This skill is intentionally generic and works across any repo — it infers context from git history and project structure rather than assuming a specific setup.
Commit message format, logical grouping, and branch naming rules. Follow when creating git commits, branches, or PRs.
commit and push all local changes to remote repo
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.
Tidy workspace, create semantically meaningful commits, and push. Analyzes changes, categorizes files (commit/gitignore/delete/consolidate), groups into logical commits with conventional prefixes. Use when: ready to commit, cleaning workspace, pushing changes.
This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit staged/unstaged changes following conventional commits format
Generate release notes from commits since last tag
A skill for writing Git commit messages. It follows rules combining Conventional Commits and Gitmoji to maintain a consistent commit history.
Create standardized git commits using Conventional Commits with Gitmoji. Use when the user asks to commit changes, create a commit, or says "/commit". Analyzes staged/unstaged diffs and generates semantic commit messages with emoji prefixes.