Total 30,488 skills, Version Control has 596 skills
Showing 12 of 596 skills
[Git] Resolve git merge/cherry-pick/rebase conflicts with backup, analysis, and reporting
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step. TRIGGERS - contribute, feature branch, create PR, submit PR, git-town contribute.
Generates structured changelogs and release notes from git history and PR descriptions. Classifies changes into breaking, features, fixes, performance, and docs. Filters internal-only changes, detects breaking changes, and produces human-readable entries linked to source PRs. Triggers on: "generate changelog", "write release notes", "compose changelog", "what changed since", "changes since last release", "prepare release", "release notes for", "changelog for", "summarize changes", "diff since tag". Use this skill when preparing a release and needing to summarize changes for users.
Create a feature branch in a git worktree from a GitHub issue
This skill should be used when you need to create, open, or edit a pull request (PR), or the user asks to "create a PR", "open a PR", "submit a PR", "raise a PR", "file a PR", "make a PR", "create a pull request", "open a pull request", "new PR", or any variation requesting GitHub pull request creation.
The human project owner and final authority. Does not write code or run tools -- resolves tie-breaks, approves or denies major decisions, and unblocks deadlocks.
A fiscally disciplined finance leader who monitors provider spend, forecasts burn against budget, and enforces cost controls.
Analyze how code changed over time. Use when investigating regressions, understanding why code was written a certain way, or finding when a behavior changed.
Analyzes files modified with git commands and creates appropriately granular commits in logical units. Only activates when the skill name (committer) is explicitly specified, such as "/committer", "use the committer skill", or "commit with committer". Does not activate for general requests like "commit" or "git commit".
Use when a repo has `.xit/` or the user asks for xit: translate git-like intents to non-interactive `xit` CLI commands (`status/diff/log --cli`, add/commit/branch/merge/cherry-pick), avoid the TUI, and do not use git unless explicitly requested.
Stage 2 (REX mode only) — Git archaeology, changelog analysis, verified factual timeline. Skip automatically in Concept mode.
Smart commit creation with conventional commits. Use when user says "commit" or requests committing changes. Handles staged file detection, suggests splits for multi-concern changes, and applies proper commit format without emoji prefixes.