Loading...
Loading...
Found 174 Skills
Generate a git commit message and ready-to-run git commit command from the actual staged/working diff. Use whenever the user asks for a commit message, commit command, "/git-commit", or "commit this"; supports one-line commits, detailed commits, single-repo projects, and monorepo scoped commit bodies.
Cut a release from the Conventional Commits a repo already writes: derive the semver bump and a changelog from the commit range, bump the manifest, tag it, and publish a GitHub release, all behind a mandatory preview. Use when the user says "cut a release", "tag a version", "release this", "what's the next version", "generate a changelog", "ship v2", or "/releasekit". It never publishes to a package registry and never moves a published tag.
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.
Write clear, conventional commit messages with proper type prefixes, scopes, and body content.
Smart Commit - stages all changes and creates a conventional commit
Creates and validates semantic Git commit messages using Conventional Commits, based on the actual staged diff and repository history. Use for commit messages, semantic commits, conventional commits, changelog-friendly history, or preparing a requested commit. Do not commit or push unless the user explicitly asks.