Loading...
Loading...
Found 193 Skills
Stage and commit the intended changes with a clear message.
Use when writing or editing a pull request title or body.
Writes a conventional commit message for what the user has staged, matching the types and scopes in the repo's own git log, runs the project's CI lint on the staged files only, shows the message for review, and commits only after the user confirms. Respects the user's staging, warns about secret-looking or scratch files, and suggests splitting diffs that mix unrelated changes. Use when the user says /generate-commit, "write a commit message", "commit what I staged", "commit this", or wants a reviewed conventional commit.
Commits with perfect messages. Use when making a commit.
Understand auto-generated changelogs via semantic-release. Use when viewing release history, understanding changelog format, or debugging missing changelog entries.
Manages git operations (branching, committing, pushing) across multi-repo systems with git submodules. Use this skill whenever the user wants to create a feature branch, commit changes, push code, sync submodules, or manage branches across the parent repo and service repos. Also use when implementing BMAD stories that touch one or more services, or when the user asks about git workflow in a multi-repo project. Triggers on phrases like "create branch", "commit changes", "push to remote", "sync submodules", "start working on story", "update service branch", or any git operation that spans parent and submodule repos.
Detects and prevents manual edits to release-please managed files (CHANGELOG.md, version fields in package.json, pyproject.toml, Cargo.toml). Provides conventional commit templates. Use when editing changelogs, version bumps, release files, or when user mentions "release", "changelog", "version bump", or "conventional commits".
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Create git commits using conventional commits with scopes. Use when the user asks to commit, make a commit, save changes, or any git commit operation. Never include Co-Authored-By lines, AI agent mentions, or any reference to Claude, AI, or automated tooling in commit messages.
Use When: Submitting code to a Git repository and generating standardized commit messages
Generate changelogs, release notes, and migration guides from git history. Parse conventional commits. Use for releases. NOT for git ops (git-workflow) or doc sites (docs-steward).
Create and execute Git commits in Conventional Commits format with a required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.