Total 30,497 skills, Version Control has 598 skills
Showing 12 of 598 skills
Create one or more Conventional Commits following the spec and push the current branch. Use when the user asks to create commits, write a conventional commit message, commit and push changes, or prepare commits before opening a pull request.
Assists in creating, modifying, viewing or managing GitHub Pull Request (PR). Automatically analyzes branch commits and change content, generates compliant Traditional Chinese PR titles and descriptions. Use cases include: (1) Create a new PR from the current branch, (2) Modify the title, description, reviewers or labels of an existing PR, (3) Check the PR status of the branch (open, merged, closed), (4) Need to automatically aggregate multiple changes to generate a summary. Applicable to scenarios with requests such as "create PR", "create pull request", "help me open a PR", "modify PR content". Operations are executed via GitHub CLI (gh).
(hal-9000) Use when editing any file under plugins/hal-voice/ to bump the plugin version before committing
Commit and push ALL changes (staged + unstaged + untracked) to the remote repository
Git commit message best practices. Use when writing commit messages, reviewing commits, or setting up commit conventions for a project. Ensures clear, consistent, and useful commit history.
Implement a feature from issue, specs, and docs, then propose a PR
Generate professional git commit messages following cbea.ms guidelines. Outputs plain copy-pasteable commit message text by default.
Parallel development with git worktrees and Claude Code agents. Handles Ghostty terminal launching, port allocation, and global registry. Use when creating worktrees, managing parallel development, or launching agents in isolated workspaces.
GitHub workflow for ToolUniverse - push code safely by moving temp files, activating pre-commit hooks, running tests, and cleaning staged files. Use when pushing to GitHub, fixing CI failures, or cleaning up before commits.
Use when you need to work on multiple branches simultaneously, run parallel Claude Code sessions, handle emergency hotfixes during feature work, review PRs without switching branches, or test across branches without losing current work. Use when asked to "work on two branches at once", "parallel development", "switch without losing work", "create a worktree", or "hotfix while working on a feature".
Branch and PR workflow for Engram contributors. Trigger: When starting any change that will be proposed through GitHub.
Commit standards for Engram contributors. Trigger: Any commit creation, review, or branch cleanup.