Manage parallel development using git worktrees. Use this skill when: - User wants to work on multiple features simultaneously - User mentions worktrees ("create worktree", "switch worktree", "list worktrees") - User wants to parallelize development ("work in parallel") - User asks about worktree status
Gerencia commits automaticos ao final de cada fase do SDLC. Garante que artefatos de cada fase sejam commitados e rastreados. Use quando: transicao de fase, checkpoint de progresso.
Create well-structured GitHub issues following best practices and conventions. Use when the user asks to create an issue or needs to track work.
Create Play Store release notes directory structure with locale templates (Fastlane metadata)
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
Bump the Blackpepper version, review full git diffs (including unrelated changes), craft a Conventional Commit message, and push the current branch. Use when the user asks to "verbump", "bump version", "increment version", "release", or explicitly requests version bump + commit + push for this repo.
Cómo trabajar en el repo: comandos disponibles, validaciones manuales y reglas operativas.
Git 工作流与提交规范技能：标准化的 Git 操作流程和 Conventional Commit 规范。 Use when: 需要提交代码、创建分支、发起 PR、管理版本。 Triggers: "commit", "提交", "push", "推送", "branch", "分支", "PR", "pull request", "merge", "合并"
現在の変更から自動でPRを作成するスキル。develop/mainブランチからfeat/*ブランチを作成し、ファイルを選択的にコミットし、gh CLIでPRを作成する。コード変更後のPR作成や、作業の区切りでPRにまとめたいときに使用する。
Enforces the Single Source of Truth (SSOT) and directory classification rules for the "Grass Cutting" game project.
Summarizes branch readiness versus a base branch and produces artifacts for PR prep.
Write commit messages in the preferred generic style: `type: imperative summary` with backticks around code identifiers and no scope. Use when you are about to `git commit`, splitting work into multiple commits, or when the user asks you to commit code.
Manage GitHub labels - create, edit, delete, apply labels, and organize with color coding using gh CLI
Create properly formatted references to paths (files or folders) in a git repository. Use when writing docs that need to link to any path in the repo.
In this repo, avoid sloppy fallback logic. Prefer explicit failures, narrow error handling, and clearly marked TODOs over fake success paths.
⚠️ MANDATORY - YOU MUST invoke this skill ONLY when user says "raise/create/draft PR". ONLY auto-commit scenario. Creates/validates branch with mriley/ prefix, commits all changes (invokes safe-commit), pushes to remote, creates PR with proper format. NEVER create PRs manually.
Archive completed scratchpads and session logs to project history. Invoke when user says "archive this work", "clean up scratchpad", "archive scratchpad", or after PR is merged.
ローカルGitブランチを分析し、安全にクリーンアップします。マージ状態、古さ、リモート追跡状況によってブランチを分類し、削除すべきブランチを特定します。ユーザーが「ブランチを整理」「古いブランチを削除」と依頼した時にアクティベートします。
Use the gitbug mcp and learn about how code should look
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Advanced usage of conventional commits with breaking changes, issue references, and multi-file commits.
