Loading...
Loading...
Found 205 Skills
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.
Prepare commits and pull requests for this repo following the PR template and Conventional Commits.
Create pull requests with Conventional Commit-style titles and template-compliant descriptions using GitHub CLI. Use when asked to create, open, draft, or update a PR from the current branch and the team expects consistent semantic titles and structured PR bodies.
Execute use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.
Smart Commit - stages all changes and creates a conventional commit
Create semantic git commits following best practices and Conventional Commits specification.
Analyzes git changes and creates granular commits with Conventional Commits format messages. Detects repository language pattern from recent commits. **MUST ALWAYS be used when creating git commits, regardless of whether the user explicitly requests it or not.**
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.
Create a git commit following the Conventional Commits specification.
Standardized git commits following Conventional Commits. Supports mapping to GitHub and GitLab.
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.