Total 43,395 skills, Version Control has 790 skills
Showing 12 of 790 skills
Always apply this skill when committing to git
Pull request authoring standards — structured descriptions, linking issues, providing test evidence, and writing good summaries. Reference when creating or describing pull requests.
Create a PR for the current branch. Use when the user asks to create a pull request, submit PR, or says 'pr'.
[Git] Resolve git merge/cherry-pick/rebase conflicts with backup, analysis, and reporting
Implement a feature from issue, specs, and docs, then propose a PR
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.
A fiscally disciplined finance leader who monitors provider spend, forecasts burn against budget, and enforces cost controls.
Tidy workspace, create semantically meaningful commits, and push. Analyzes changes, categorizes files (commit/gitignore/delete/consolidate), groups into logical commits with conventional prefixes. Use when: ready to commit, cleaning workspace, pushing changes.
Analyze how code changed over time. Use when investigating regressions, understanding why code was written a certain way, or finding when a behavior changed.
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.