Loading...
Loading...
Found 124 Skills
Git worktree management for parallel agent team development. Triggers: 'create worktree', 'worktree setup', or during /delegate dispatch. Do NOT use for branch creation without delegation context.
Create git commit messages based on current staged changes. Has support for git emoji messages.
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or runs /create-pr or /pr-creator commands.
Git workflow patterns for commits, branching, PRs, and history management across heterogeneous repositories. Use when creating commits, managing branches, opening pull requests, or rewriting history. Do not use for non-git implementation tasks or repo-specific release policy decisions without repository documentation.
This skill should be used when working with Graphite (gt) for stacked pull requests. Use when users mention gt commands, stack management, PR workflows, or when dealing with dependent branches. Essential for understanding stack navigation, branch relationships, and Graphite's mental model.
タスク完了後に自律的に実行する必要があるフロースキルです。 Trigger: task completed, ready to submit code
Create or update a feature specification from a natural language feature description.
Use this skill when managing git branches, releases, or hotfixes according to the Gitflow workflow. It enforces naming conventions and synchronization policies.
Create and setup git worktrees for parallel development with automatic dependency installation
Create well-formatted commits with conventional commit messages and emoji
Manage parallel development with cmux-style git worktrees in one repository. Use this skill whenever the user asks to run multiple agents in parallel, create or resume isolated worktrees, list/switch/merge/remove worktrees, set up `.cmux/setup`, or recover from worktree conflicts. In this environment, always use the `cmx` alias in commands.
Used when the current Spec Pack needs to be discarded/revoked due to major requirement issues, and the corresponding `.aisdlc/specs/{branch}` directory as well as local and remote branches must be deleted. Meanwhile, you need to output the deletion list and ask the user for double confirmation before performing the deletion.