Loading...
Loading...
Found 519 Skills
Guidelines for git and GitHub operations in the WooCommerce repository.
Finalize GitHub PRs end-to-end: update branch/PR, monitor CI until green, squash-merge, and clean up local/remote state. Use when asked to $fin or to finish/land/merge/close a PR, watch checks or runs, squash-merge, delete the branch, and sync local state.
Create a well-formatted commit message from staged changes
Git workflow and branching strategy expert. Use when establishing team collaboration patterns, optimizing commit practices, or designing scalable version control workflows for better developer experience.
Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /review-pr. Never merge or push to main.
Test, commit, and push in one atomic workflow. Runs Go and Python tests, commits with conventional message, pushes to current branch.
Automated Git Commits
Creates a git worktree from main for a Linear issue. Use when the user pastes a Linear URL (https://linear.app/.../issue/ABC-58/...), a Linear "copy as prompt" string, or just an issue ID like "ABC-58". Handles URL parsing, branch name derivation, and worktree creation as a sibling directory. Also use when asked to "make a worktree for ABC-58", "set up a branch for this issue", or "create a worktree".
Generate professional git commit messages following cbea.ms guidelines. Outputs plain copy-pasteable commit message text by default.
Commit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", "commit push PR", or wants to go from working changes to an open pull request in one step. Produces PR descriptions that scale in depth with the complexity of the change, avoiding cookie-cutter templates.
[Hyper] Create one or more Conventional Commits from the current repository state. Inspect staged and unstaged changes, group them into logical change sets, generate a compliant message per group, and commit each group separately in sequence.
Cria mensagens de commit no estilo Conventional Commits — usar quando o usuário pede "commit", "git commit", ou após mudanças prontas para serem registradas no histórico.