conventional-commit
Gitの変更を検出してConventional Commits形式で日本語コミットメッセージを自動生成・実行するスキル。コード変更後やユーザーが「コミットして」「変更を保存」などと発言したときに使用する。git add、git commit、変更の分析を含む。
Gitの変更を検出してConventional Commits形式で日本語コミットメッセージを自動生成・実行するスキル。コード変更後やユーザーが「コミットして」「変更を保存」などと発言したときに使用する。git add、git commit、変更の分析を含む。
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布, documentation, 同步文件, 文件檢查, doc check, 發布前, before release, 準備發布.
Clean up git branches marked as [gone] that have been deleted on the remote but still exist locally.
Generates clear commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or when the user asks to create a commit.
Run `codex review` plus PAL `codereview` (via the `pal-mcporter` skill) against a git base ref, then merge both outputs into one prioritized, actionable review.
Generate conventional commit messages following best practices. Use when creating structured git commit messages.
This skill should be used when the user says "commit changes", "commit this", "commit my work", "save to git", "save my changes", "push this", "push my work", "create a commit", or wants to save their work to version control. Handles the full git workflow including staging, committing, and pushing.
GitHub CLI authentication and GraphQL API usage for safe GitHub operations
Use when creating "changelog", "release notes", "version updates", generating "CHANGELOG.md", or asking about "git history to changelog", "commit summary", "what changed since last release"
This skill should be used when reviewing GitHub Pull Requests to provide comprehensive code quality, security, and architecture analysis with optional JIRA ticket integration.
SEMPRE use esta skill quando usuario pedir para fazer commit, commitar, criar commit, ou escrever mensagem de commit. Analisa git diffs e gera mensagens seguindo Conventional Commits.
Create (draft) pull requests on GitHub. Use when user requests to create a pr, pull request, draft pr, draft pull request.
Create a git commit, push a branch, and open a Pull Request with gh. Use when asked to commit changes, push to origin, or create PRs, especially when conventional commits and PR templates are required.
Create a git commit with a short message (up to 50 characters). Use when the user asks to commit changes with a short/concise message.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification