git-plugin

Specialized agent for complex git write operations. Handles merge conflicts, rebases, cherry-picks, bisect, and multi-step git workflows. Use when git operations are verbose or multi-step (conflict resolution, rebase with conflicts, bisect) to keep that output isolated from the main context.

GitHub CLI commands optimized for AI agent workflows with JSON output and deterministic execution patterns.

Monitor GitHub Actions workflow runs using blocking watch commands instead of polling with timeouts.

Create PRs via GitHub API without local git operations. Use when you want to submit file changes as a PR without committing locally — for quick fixes, typos, config updates, or when you want a clean workflow that bypasses local git state entirely.

Git branch naming conventions for consistent, traceable branches. Use when creating new branches, discussing branch naming standards, or setting up repository conventions. Covers type prefixes (feat, fix, chore), issue linking, and kebab-case formatting.

Branch management, pull request workflows, and GitHub integration. Main-branch development pattern (push main to remote feature branches), modern Git commands (switch, restore), and GitHub MCP tools. Use when user mentions creating branches, opening PRs, git switch, git restore, feature branches, pull requests, or GitHub PR workflows. For naming conventions see git-branch-naming, for rebase patterns see git-rebase-patterns.

Git commands optimized for AI agent workflows with porcelain output and deterministic execution patterns.

- Pre-commit config: !`find . -maxdepth 1 -name ".pre-commit-config.yaml"`

Git commit trailer conventions and patterns. Use when composing commit messages that need BREAKING CHANGE, Release-As, Co-authored-by, Signed-off-by, or other trailer lines. Covers release-please trailers for version control, attribution trailers, and git interpret-trailers for parsing and adding trailers programmatically.

Commit message conventions, staging practices, and commit best practices. Covers conventional commits, explicit staging workflow, logical change grouping, humble fact-based communication style, and automatic issue detection. Use when user mentions committing changes, writing commit messages, git add, git commit, staging files, or conventional commit format.

Create commits with conventional messages and issue references. Handles staging, pre-commit hooks, and automatic issue detection. Use when user says "commit", "commit locally", "save changes", "stage and commit", or similar. This skill creates local commits only - see git-push for remote operations.

Resolve merge conflicts. Use when a merge or rebase has conflicts, a PR can't merge, "fix conflicts" appears, or you need to reconcile diverged branches. Handles file-by-file resolution with modern git tooling.

- Current branch: !`git branch --show-current`

- Repo: !`git remote get-url origin`

Fork management and upstream synchronization. Use when working with forked repositories, syncing fork with upstream, managing divergence between fork and upstream, or preparing commits for upstream contribution. Covers remote architecture, divergence detection, sync strategies, and cross-fork PRs. For creating upstream PRs, see git-upstream-pr.

Manage sub-issues and dependency relationships between GitHub issues. Use when breaking issues into sub-tasks, checking sub-issue completion progress, or marking blocking/blocked-by dependencies between issues.

Administrative operations on GitHub issues. Use when transferring issues between repos, pinning important issues, locking resolved discussions, creating development branches from issues, performing bulk operations, or managing custom issue fields.

- Repo: !`git remote get-url origin`

- Current branch: !`git branch --show-current`

- Repo: !`git remote -v`

Create pull requests with proper descriptions, labels, and issue references. Handles draft mode, reviewers, and base branch selection. Use when user says "create PR", "open pull request", "submit for review", or similar. This skill creates PRs from pushed branches - see git-commit for commits and git-push for pushing.

Push local commits to remote repositories. Handles branch tracking, upstream setup, and safe push patterns. Use when user says "push", "push changes", "send to remote", "update remote", or similar. This skill pushes existing commits - see git-commit for creating commits and git-pr for pull request creation.

Advanced git rebase patterns for linear history, stacked PRs, and clean commit management. Use when rebasing branches, cleaning up commit history, managing PR stacks, or converting merge-heavy branches to linear history. Covers --reapply-cherry-picks, --update-refs, --onto, and interactive rebase workflows.

Detect GitHub repository name and owner from git remotes. Use when needing repo identifier for GitHub CLI, API calls, or when working with multiple repositories. Automatically extracts owner/repo format.

Resolve merge conflicts in pull requests. Use when a PR has merge conflicts with its base branch, when rebasing produces conflicts, or when automated merges fail due to conflicting changes.

Pre-commit security validation and secret detection. Runs gitleaks scan and validates configuration, integrates with pre-commit hooks to prevent credential leaks. Use when user mentions scanning for secrets, gitleaks, secret detection, credential scanning, pre-commit security, or .gitleaks.toml.

Submit clean PRs to upstream repositories from a fork. Use when you need to contribute changes back to the original repo, cherry-pick fork commits for upstream, or create cross-fork pull requests. Handles branch creation from upstream/main, commit selection, squashing, and cross-fork PR creation.

Automatically detect GitHub issues that staged changes may fix or close. Analyzes diffs, file paths, and issue metadata to suggest appropriate closing keywords (Fixes, Closes, Resolves) for commit messages. Use when committing changes to ensure proper issue linkage.

Create well-structured GitHub issues with clear titles, descriptions, and acceptance criteria. Use when filing bugs, requesting features, or structuring issue content.

Discover and apply labels to GitHub PRs and issues using the gh CLI. Use when you need to list available labels, add or remove labels on pull requests or issues, or create new labels for a repository. Trigger phrases: "label this PR", "add labels to issue", "what labels are available", "create a new label".

Craft PR titles using conventional commits format. Use when creating PRs or ensuring consistent PR naming. PR titles MUST follow conventional commits to drive release-please automation and maintain consistent git history.

Configures release-please for monorepos and single-package repos. Handles manifest files, component tagging, changelog sections, and extra-files setup. Use when setting up automated releases, fixing release workflow issues, or configuring version bump automation.

Manages release-please PR merging workflow for monorepos. Handles batch merging, conflict resolution through PR closure/recreation, and iterative processing until all PRs are merged. Use when merging release PRs, handling PR conflicts, or managing release automation in monorepos.

Detects and prevents manual edits to release-please managed files (CHANGELOG.md, version fields in package.json, pyproject.toml, Cargo.toml). Provides conventional commit templates. Use when editing changelogs, version bumps, release files, or when user mentions "release", "changelog", "version bump", or "conventional commits".

2 hooks across 1 event