Loading...
Loading...
Found 229 Skills
Stage changes, draft conventional commit messages, and commit with user confirmation. Use when user types /commit, asks to commit changes, or mentions creating a git commit.
GitHub PR の CI ステータス (`gh pr checks`)・コード品質・セキュリティ (OWASP Top 10)・Conventional Commits 準拠をレビューする。`gh pr review --approve/--request-changes/--comment` でレビュー投稿も可能。「PR #N をレビュー」「PR レビューして」などで使用。ローカル diff のレビューには implement-review を使用。
Cria mensagens de commit no estilo Conventional Commits — usar quando o usuário pede "commit", "git commit", ou após mudanças prontas para serem registradas no histórico.
Generate git commits following Conventional Commits (commitlint). Use when user wants to commit changes.
Create semantic git commits following Conventional Commits specification. Use when committing changes, making commits, or when asked to commit.
Create well-formatted commits with conventional commit messages and emoji
Smart commit creation with conventional commits. Use when user says "commit" or requests committing changes. Handles staged file detection, suggests splits for multi-concern changes, and applies proper commit format without emoji prefixes.
Automates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates.
PR creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
Generate and validate Git branch names from commit messages or descriptions. Use when creating branches, generating names for /pr-sync, validating existing branch names, or converting conventional commits to branch prefixes. Triggers: "branch name", "create branch", "name this branch", "validate branch". Do NOT use for git operations (checkout, merge, delete), branching strategies, or branch protection rules.
Generate structured, professional Release Notes / Changelog from a raw commit log. Automatically categorizes commits into Breaking Changes, Features, and Fixes. Trigger when the user asks to write release notes or a changelog based on provided text.
Smart Commit - stages all changes and creates a conventional commit