sharing-skills
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
git-worktrees
Use when working on multiple features simultaneously. Creates isolated workspaces without branch switching, enabling parallel development.
advanced-git
Advanced Git - interactive rebase, cherry-pick, bisect, reflog, and power user operations
julien-troubleshooting-onedrive-reserved
This skill should be used when the user reports OneDrive sync errors caused by Windows reserved filenames (NUL, CON, PRN, AUX, COM1-9, LPT1-9). It efficiently locates and removes these undeletable files using Git Bash.
code-review
Perform elite PR review with confidence scores and post to GitHub
git-commit
適切な粒度でコミット作成スキル。変更内容を機能・目的ごとに分割し、複数の小さなコミットを作成。Use when: コミット作成、変更のコミット、適切な粒度でのコミットを依頼された時。
git-safety-guard
Blocks destructive git and filesystem commands before execution. Prevents accidental loss of uncommitted work from git checkout --, git reset --hard, rm -rf, and similar destructive operations. Works as a Codex CLI PreToolUse hook with fail-open semantics.
forked-package-management
Git submodules, VCS path repositories, and custom package development for pcrcard/* namespace packages
project-initializer
Initialize new projects with best practices. Use when starting new codebases or setting up repos.
repo-security-purge
Rewrites git history to permanently remove sensitive data. DESTRUCTIVE OPERATION - rewrites commit history. Use when user asks to "purge secrets from history", "remove sensitive data from git history", "clean git history", or "/repo-security-purge". Requires explicit confirmation.
sc-startup
Run repo startup: prompt load, checklist sync, optional PR triage, worktree hygiene, and CI pull. Best-effort with structured status.
receiving-code-review
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
setup-runner
GitHub 設定ファイルをセットアップする。「GitHub 設定をセットアップ」「.github を作って」「Issue テンプレート作成」「PR テンプレート作成」「GitHub 設定を初期化」「リポジトリ設定をセットアップ」「ラベル設定を作成」などで起動。.github ディレクトリに必要な設定ファイルを一括生成。
finishing-a-development-branch
Use when ready to merge feature branch. Complete checklist before creating PR/MR. Ensures professional quality and prevents embarrassing mistakes.
branch-creator
Issue 番号に基づいて feature ブランチを自動作成する。「ブランチ作成」「ブランチを作って」「新しいブランチ」「feature ブランチ」「Issue からブランチ」「作業ブランチを作成」「ブランチ切って」などで起動。feature/[issue番号] 形式でブランチを作成。
sc-managing-github-issues
GitHub issue lifecycle management with worktree isolation
gh-pr-handling
Expert GitHub CLI and PR handling. Use when working with pull requests, GitHub issues, reviews, CI checks, or any gh command operations.
polishing-issues
Make a GitHub issue self-contained for a single feature/fix so any coding agent can execute it without back-and-forth. Focus on scope, file touchpoints, acceptance criteria, and validation.
finishing-a-development-branch
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
