Loading...
Loading...
Found 239 Skills
This skill should be used when creating Git commits to ensure they follow the Conventional Commits specification. It provides guidance on commit message structure, types, scopes, and best practices for writing clear, consistent, and automated-friendly commit messages. Use when committing code changes or reviewing commit history.
Create git commits following Conventional Commits specification with project-specific branch naming rules
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
Generate comprehensive release notes and changelogs. Compiles version history, feature descriptions, and breaking changes from commit information.
[Implementation] ⚡⚡ Implement a feature automatically ("trust me bro")
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or runs /commit-staged or /commit-creator commands.
Commit changes from the current Claude Code session to a new branch, push to GitHub, and open a PR. Use when the user wants to save their work as a PR, submit session changes, or create a pull request for what was done in this session.
Create git commits following repository style. Use when user asks to "create a commit", "commit changes", "/commit", or requests committing code to git.
Use when the user says /bye, "wrap up", "end session", or similar. Reconstructs full session history including compacted context, creates a sessionlog, commits changes, and summarizes next steps.
Generate professional git commit messages following cbea.ms guidelines. Outputs plain copy-pasteable commit message text by default.
Standardized git commits following Conventional Commits. Supports mapping to GitHub and GitLab.
Write, review, and validate commit messages following the Conventional Commits v1.0.0 specification. Use when: (1) crafting a git commit message for any change, (2) reviewing or correcting an existing commit message, (3) choosing the right commit type for a change, (4) deciding how to mark a breaking change, (5) writing multi-line commits with body and footers, or (6) understanding how commits map to SemVer bumps (PATCH/MINOR/MAJOR). Covers all standard types: feat, fix, docs, chore, refactor, perf, test, build, ci, style, revert.