Total 30,497 skills, Version Control has 598 skills
Showing 12 of 598 skills
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
Generate GitHub Pull Request title and description from branch changes
GitHub via Composio API. Use when: (1) Reading repository contents, README, or downloading repos (2) Creating, updating, or listing issues (3) Creating, listing, or merging pull requests (4) Listing repositories or branches DO NOT use `gh` CLI - it will fail with auth errors. Use Composio HTTP API only.
Browse and review open learning PRs in the configured groovebook repo. Use to participate in the shared groove commons.
Git and GitHub wizard using gh CLI for all git operations and GitHub interactions
Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.
This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.
ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Sentry conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR, update PR title, update PR description, edit PR, push and create PR, prepare changes for review task, or request for a PR writer.
GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
This skill should be used when the user asks to "create a pull request", "create PR", "open PR", "update a pull request", "update PR", "create an issue", "file an issue", "create a GitHub issue", "create a Claude Code issue", "report a bug in Claude Code", "create a Codex issue", "report a bug in Codex CLI", "create a Sablier issue", "file an issue in sablier-labs", "create a discussion", "start a GitHub discussion", or mentions OSS contribution workflows.
Use when squash-merging a feature branch into main for linear history. Handles pre-flight checks, squash merge, commit delegation to git-commit, and branch cleanup.