repo-create
GitHubリポジトリを新規作成・初期化。ghコマンド使用。 トリガー例: 「リポジトリを作成」「GitHubリポジトリ」「repo-create」「gh repo create」
using-git-worktrees
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
status-syncer
Forces refresh of status cache and displays comprehensive repository status to trigger statusLine update
cleanup-manager
List and delete stale branches with safety checks for merged and inactive branches
branch-pusher
Push branches to remote repository with safety checks and force-with-lease support
branch-puller
Pull branches from remote repository with intelligent conflict resolution
git-worktrees
Use when starting work that needs isolated branches or parallel feature development using git worktrees.
using-git-worktrees
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
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
project-setup
Initialize and configure new projects with proper structure and tooling
cleanup-merged-branches
Deletes local and remote git branches that have been merged into main.
spec-archiver
Archives completed specifications to cloud storage with index management, GitHub commenting, and local cleanup
commit-hooks
Git commit フック（pre-commit/commit-msg/pre-push）の設計・実装・検証を体系化するスキル。 Husky と lint-staged を軸に、品質ゲートと運用ルールを整理する。 Anchors: • Pro Git / 適用: Git Hooks設計 / 目的: フック運用の基礎 • Clean Code / 適用: 品質ゲート設計 / 目的: コミット品質の維持 • Accelerate / 適用: フィードバックループ / 目的: 継続改善 Trigger: Use when designing commit hooks, integrating husky/lint-staged, enforcing commit message rules, or validating pre-push checks. commit hooks, husky, lint-staged, commit-msg, pre-commit, pre-push
monorepo-dependency-management
モノレポ環境での依存関係管理、ワークスペース間の整合性維持を専門とするスキル。 pnpm workspaces、変更影響分析、パッケージ間バージョン同期、循環依存検出の方法論を提供する。 Anchors: • The Pragmatic Programmer (Andrew Hunt) / 適用: 実践的改善と品質維持 / 目的: モノレポの段階的構築と保守性向上 • Program Development in Java (Barbara Liskov) / 適用: 抽象化と依存関係設計 / 目的: パッケージ間の明確な境界定義 • pnpm workspace protocol / 適用: workspace:*による内部依存定義 / 目的: ワークスペース構造の標準化 Trigger: Use when managing monorepo dependencies, analyzing workspace relationships, synchronizing package versions, detecting circular dependencies, or configuring pnpm workspaces. monorepo, pnpm, workspace, dependency graph, version sync, circular dependency, hoisting, turborepo
pr-manager
Create, comment, review, approve, and merge pull requests with FABER metadata
github-api
Orchestrates comprehensive GitHub API access across all services. Intelligently routes API operations to specialized resource files covering authentication, repositories, issues/PRs, workflows, security, and more. Use when implementing GitHub integrations, automating operations, or building applications that interact with GitHub.
pre-commit-security
pre-commit hookセキュリティスキル。機密情報検出パターン、git-secrets/gitleaks統合、チーム展開戦略、Git履歴スキャンを実装し、コミット前の機密情報漏洩を防ぐ。 Anchors: • Web Application Security (Andrew Hoffman) / 適用: 脅威モデリング・セキュア設計 / 目的: セキュリティリスクの体系的評価 • OWASP Top 10 / 適用: 機密情報検出パターン設計 / 目的: 業界標準の脆弱性分類に基づくパターン定義 • git-secrets / gitleaks公式ドキュメント / 適用: ツール統合・設定 / 目的: 公式ベストプラクティスに準拠した導入 Trigger: Use when implementing pre-commit hooks for secret detection, designing detection patterns, integrating git-secrets/gitleaks, scanning Git history for leaked secrets, or deploying security hooks across teams. pre-commit security, secret detection, git-secrets, gitleaks, credential scanning, Git history scan
prompt-versioning-management
プロンプトのライフサイクル管理を専門とするスキル。バージョン管理、デプロイ戦略、ロールバック、変更追跡により、本番環境で安全かつ効率的なプロンプト運用を実現します。 Anchors: • The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 手順設計と実践的改善 / 目的: 体系的なバージョン管理 • Continuous Delivery (Jez Humble) / 適用: デプロイパイプラインとロールバック戦略 / 目的: 安全なリリースプロセス • Semantic Versioning 2.0.0 / 適用: バージョン番号付けルール / 目的: 変更の影響範囲の明確化 Trigger: Use when managing prompt versions, deploying prompts to production, implementing rollback strategies, tracking prompt changes, or establishing prompt lifecycle management. Keywords: prompt versioning, semantic versioning, deployment strategy, rollback, change tracking, prompt lifecycle, blue-green deployment