Loading...
Loading...
Found 143 Skills
Create git commit messages based on current staged changes. Has support for git emoji messages.
Git-centric implementation workflow. Enforces clean checkout, creates a properly named branch, tracks progress in a WIP markdown file, and commits/pushes continuously so remote git logs serve as the primary monitoring channel. Use when starting any plan-based implementation task.
Create a git worktree for the current repository at the same directory level as the project root. This skill automates branch creation, directory naming according to the format project-T-branch, and initial project setup (e.g., dependency installation). Use this when the user wants to work on a new feature or fix without switching their current workspace.
Create and submit Gitee pull requests with team convention enforcement. Use when the user asks to open/submit a Gitee PR on gitee.com and needs an automated flow that validates branch naming, commit prefixes, clean working tree, optional auto-commit, branch push, and PR creation.
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.
Sync local changes to GitHub in one command: detect state, branch, commit, push, create PR. Use when user wants to push work to GitHub, create a PR, or sync a feature branch. Use for "push my changes", "create a PR", "sync to GitHub", "open pull request", or "ship this". Do NOT use for reviewing PRs (use /pr-review), cleaning up after merge (use pr-cleanup), or CI checks (use ci).
Use when needing multiple checked-out branches simultaneously without re-cloning — review a PR while keeping WIP, per-branch build caches, or hotfix alongside feature work
Merge all worktrees from .trees/ into current branch and clean up
Create isolated git worktrees for parallel feature work with monorepo-aware env file copying and node_modules symlinking.
You are a **Jira Workflow Steward**, the delivery disciplinarian who refuses anonymous code. If a change cannot be traced from Jira to branch to commit to pull request to release, you treat the wor...
Implements an approved spec. Validates that the state means "Approved" (in any language), creates a git branch named after the spec, switches to it, and starts the implementation step by step with pauses to review diffs.
Create atomic user-approved commits with `feat`/`fix`/`chore` titles and finalise branch merge/cleanup with tracking sync. Triggers: commit changes, split commits, finalise branch, commit message.