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
Executes GitHub operations via gh CLI wrapper. Use when managing issues, pull requests, workflows, CI runs, projects, releases, cache, labels, or searching repositories and code.
TYPO3 Core contribution workflow. Use when working with Forge issues, submitting patches to Gerrit, or contributing docs.
Initialize PRISM .context folder in current project. Use when starting PRISM work in a new project or setting up context management.
Use when working on Fusionaly OSS or Pro - enforces clean separation between repos, prevents Pro features in OSS, forbids modifying OSS from Pro
Initializes a new epic with EPIC_TRACKING.md and story-level directory structure. Creates the foundation for managing all stories within an epic. Use when starting a new epic or when restructuring an existing epic to align with the PRD story breakdown.
Commit and push changes with gitmoji-style messages. Triggers on '/commit-push' or phrases like 'commit and push', 'save my changes', 'push this'.
Manages git operations: worktree creation, branch management, commits, PRs, semantic versioning, daily rebase workflow, and PR feedback handling. Use when: Creating branches/worktrees, committing, pushing, versioning, handling PR feedback Triggers: create worktree, commit, push, rebase, version, PR, PR feedback
Use when adding allow/deny rules to Claude Code, granting project permissions, troubleshooting "permission denied" errors, "skill requires approval" prompts, or setting up shared team permissions. Also use when working with git worktrees and permissions aren't being inherited.
Use when starting feature work that needs isolation from current workspace - creates isolated git worktrees with Flutter project setup
Analyzes GitHub repository data to generate comprehensive research reports about stars, popularity trends, and comparative insights
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
Generate comprehensive PR descriptions following repository templates
Git fundamentals - init, add, commit, status, log, and core concepts
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
BOOTSTRAP PROTOCOL: Initialize session with recent git activity, user task context, and relevant architectural decisions. Run this at the start of every coding session.
Resolves GitHub Action tags/versions (e.g., @v4) to their full 40-character commit SHAs for security pinning.
Check Pull Request on current branch, and obtain unresolved review comments. `gh` command is required. Use this when user instructed with `PR review comment` `PR レビューコメント` etc.
