This skill should be used when working with GitHub CLI (gh) for pull requests, issues, releases, and GitHub automation. Use when users mention gh commands, GitHub workflows, PR operations, issue management, or GitHub API access. Essential for understanding gh's mental model, command structure, and integration with git workflows.
Download GitHub repos as clean source code (no .git history) to WORKDIR. Do not use in a monorepo.
新しいブランチとworktreeを作成し、開発作業を開始するためのスキル。タスク着手時に「worktreeを作成」「ブランチを作成して作業開始」「/worktree-create <branch-name>」などで使用。
A skill to set up and manage a working directory for development tasks
Merge feature branch to main with pre-merge checks, CHANGELOG and ARCHITECTURE updates. Use when all spec stages are complete and user wants to merge. Ensures quality gates pass before merge.
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
作業進捗をGitHub issueに自動報告します。計画立案時、知見獲得時、問題発覚時にブランチ名からissue番号を抽出し、構造化されたコメントを投稿します。
Show GitHub connection status for current project. Requires authentication
A suite of skills to manage the full development lifecycle from start to finish. - `start-feature`: Initializes a new feature branch, docs, and story. - `sync-feature`: Saves work with CI checks. - `finish-feature`: Verifies and creates a pull request.
Clean up after a feature branch or experiment is complete. This skill deletes the git worktree and branch ONLY AFTER the associated PR has been merged. It also closes any related GitHub issues. Use this after your PR has been merged to keep the repository clean.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Create atomic commits grouped by logical features with README.md and CLAUDE.md awareness.
Guide completion of development work by presenting merge/PR options. Use when "I'm done", "merge this", "create PR", "finish up", or when implementation is complete and tests pass.
File naming, path standards, and conventional commits. Use when naming files, creating branches, writing commit messages, or setting up new projects. Covers underscore vs hyphen conventions, commit format, and branch naming patterns.
Retrieve code diff from a local git commit. Use this as the first step in a code review pipeline when reviewing local commits.
Keep Unity repos stable for CI/CD with proper gitignore, LFS, and project settings
Safe Beads workflow helper (warning-only). Use before bd sync/close/create to avoid JSONL conflicts. Ensures you are on a feature branch, up to date with origin/master, and stages Beads files cleanly with Feature-Key commits.
Prepare a pull request title/body from a Beads task (optionally using gh)
When editing KINTSUGI notebook modules (Kdecon, Kstitch, Kreg, etc.), always edit the main repo first then sync to project folders
