git-plugin

Plugin git-plugin from marketplace laurigates-claude-plugins in laurigates/claude-plugins. Commands read from the repo's manifest — today.

Skills (49)

• deadbranch

  deadbranch CLI for stale-branch cleanup — dry-run preview, TUI or non-interactive delete, protects main/develop/WIP. Use when asked to clean up branches, prune branches, or remove stale branches.

• external-pr-trust

  Authorship as a precondition of merging — bot vs stranger classification, what a merge executes, the merge-guard hook. Use when bulk-merging PRs, or when a merge is denied for a non-self author.

• gh-cli-agentic

  gh CLI commands with JSON output for agents. Use when querying PRs, issues, runs, or repo metadata; inspecting PR checks; fetching failed CI logs; or mapping a github.com URL to an API call.

• gh-workflow-monitoring

  `gh run watch` — block until a GitHub Actions run finishes, no polling loop. Use when waiting for CI after a push or following a triggered workflow to completion.

• git-api-pr

  GitHub API PR creation without local git. Use when submitting file changes as a PR without local commits — quick fixes, typos, config updates, or bypassing local git state.

• git-branch-naming

  Branch names: type prefix (feat/, fix/, chore/), issue number, kebab-case. Use when picking a name for a new branch or setting a repo's branch-naming convention.

• git-branch-pr-workflow

  Branch management and PR workflows — git switch/restore, GitHub MCP. Use when creating branches, opening PRs, or working with feature branches.

• git-cli-agentic

  Machine-readable git output for scripts: status --porcelain=v2, diff --numstat, log --format placeholders, ahead/behind counts. Use when a script or agent parses git state, not to make a commit.

• git-commit-push-pr

  End-to-end commit-to-PR workflow. Use when the user says \"create pr\", \"commit and pr\", \"push and pr\", or wants to go from uncommitted changes to an open PR.

• git-commit-trailers

  Commit trailer lines: BREAKING CHANGE, Release-As, Co-authored-by, Signed-off-by, parsed with git interpret-trailers. Use when adding, auditing, or parsing trailers in a commit message.

• git-commit-workflow

  Commit-message and staging conventions: type(scope): subject, logical grouping, explicit-path staging. Reference only, makes no commit. Use when deciding how to word a message or split changes.

• git-commit

  Local commits only: stage the changes, write a conventional message, run pre-commit, create the commit. Use when the user says \"commit\", \"save my work\", or \"stage and commit\". Pushing is git-push.

• git-conflicts

  Resolve merge conflicts file-by-file. Use when a merge/rebase has conflicts, a PR can't merge, \"fix conflicts\" is requested, or branches have diverged.

• git-coworker-check

  Detect coworker Claude agents in a shared checkout. Use when starting a session in a shared clone, before destructive git ops (stash, reset, checkout), or before bulk-edit / commit-loop workflows.

• git-derive-docs

  Derive ADRs, rules, PRDs from git commit history. Use when finding doc gaps, detecting unrecorded decisions, deriving conventions from commits, or generating skeleton docs.

• git-fix-pr

  Failing PR checks — reproduce locally, patch the code, push the fix. Use when asked to fix a PR, resolve red CI, or auto-fix lint/test failures.

• git-fork-workflow

  Fork management and upstream sync. Use when working with forks, syncing with upstream, detecting divergence, or preparing commits for contribution.

• git-issue-hierarchy

  GitHub sub-issues and blocked_by/blocking links. Use when breaking an issue into sub-tasks, checking parent progress, or viewing a dependency graph.

• git-issue-manage

  Transfer, pin, lock, or open a dev branch from a GitHub issue. Use when moving an issue between repos, pinning or locking it, or bulk-editing custom fields.

• git-issue-scoping

  Read an issue's full comment thread and re-verify its cited evidence at HEAD. Use when scoping a PR or plan from a GitHub issue, or before filing or reversing one in your own tracker.

• git-issue

  GitHub issue to PR end-to-end — branch, TDD implementation, PR — one issue or several in parallel. Use when asked to work on an issue, fix issue #N, or batch-process several.

• git-local-hazards

  Local git traps where a green command is wrong. Use when branching after a squash-merge, cutting a PR branch, after a clean merge or rebase, when a staged file vanishes, or before reset --hard.

• git-maintain

  Repo maintenance — incremental repack, gc, branch pruning, stash cleanup, fsck. Use when asked to clean up the repo, run git maintenance/gc, delete merged branches, prune stashes, or shrink .git.

• git-merge-driver

  Write a custom git merge driver that merges a file's structure instead of its lines. Use when a tool-rewritten JSON/YAML/lock file keeps conflicting on mechanical fields.

• git-merge-hazards

  Traps in GitHub's merge machinery. Use when merging a PR, merging a stacked or serial PR chain, auditing whether a branch really landed, or merging over red CI.

• git-pr-feedback

  Address PR review comments and resolve threads. Use when CHANGES_REQUESTED is set, working through unresolved review threads, or replying to reviewer feedback.

• git-pr-sync-check

  Checks whether the current PR branch is still live and in sync (merged/behind/changes-requested). Use when continuing work on a PR branch before adding commits.

• git-pr-watch

  Subscribe to a PR's activity; fix CI as it arrives and surface review threads for the user. Use when watching/monitoring/babysitting a PR after opening it, or unsubscribing with --unsubscribe.

• git-pr

  From an already-pushed branch: open the pull request with body, labels, reviewers and issue refs. Use when the user says \"create PR\", \"open pull request\", or \"submit for review\".

• git-push

  Existing commits only: push them to the remote with upstream tracking and --force-with-lease. Use when the user says \"push\", \"send to remote\", or \"update remote\". Commits nothing.

• git-rebase-patterns

  Advanced git rebase — linear history, stacked PRs, --update-refs, --onto. Use when rebasing branches, cleaning history, managing PR stacks, or fixing merge-heavy branches.

• git-repo-delete-check

  Verify a repo's work survives deletion — remote, unpushed commits, stashes — then offer a push or tar backup. Use when asked to rm -rf, delete, or prune a git checkout.

• git-repo-detection

  Detect GitHub repo owner/name from git remotes. Use when needing the owner/repo identifier for GitHub CLI or API calls, especially across multiple repos.

• git-security-checks

  Pre-commit security validation and secret detection via gitleaks. Use when scanning for secrets, setting up gitleaks, or configuring .gitleaks.toml pre-commit security.

• git-stacked-prs

  GitHub native stacked PRs via gh stack. Use when creating, syncing, rebasing or merging a PR stack, or choosing stacks vs manual PR chains.

• git-triage

  Backlog sweep over open issues and PRs — staleness, cross-links, close/merge recommendations, no code changes. Use when grooming the backlog, deciding what to close, or pre-release cleanup.

• git-upstream-fix-check

  Check upstream HEAD before patching vendored, tarball-installed, or forked code. Use when patching a dependency, custom node, or fork you don't own.

• git-upstream-pr-diverged

  Submit a diverged-fork commit to upstream as a clean PR via cherry-pick with re-derive fallback, message scrubbing, and regression checks. Use when direct rebase fails.

• git-upstream-pr

  Submit PRs to upstream repos from a fork — commit selection, squashing, cross-fork creation. Use when contributing changes upstream or cherry-picking fork commits.

• github-comment-content

  Decide what a PR or issue comment says — cut every fact the GitHub page already renders, keep what it cannot show. Use when writing a PR/issue comment, or briefing a cold-read gate on one.

• github-issue-autodetect

  Fixes/Closes/Refs keywords for a change: match the staged diff against open issues by path, label and title. Use when deciding which issue a change closes before its message is written.

• github-issue-writing

  GitHub issue body and `[Type] Component:` title — bug/feature templates, repro steps, acceptance criteria. Use when filing a bug or feature request with gh.

• github-labels

  GitHub labels via gh CLI and the build:/area:/needs: taxonomy. Use when labeling a PR or issue, checking which labels a repo has, or creating a label.

• github-pr-title

  PR title only: the type(scope): subject line that squash-merge lands on main and release-please parses. Use when writing, fixing, or validating the title of a PR.

• release-please-configuration

  release-please monorepo config — component tags, per-package extra-files, tag migration. Use when adding packages or fixing duplicate-tag / no-bump failures.

• release-please-pr-workflow

  Merging release-please release PRs — batch merge, conflict resolution by closing and recreating the PR. Use when release PRs pile up or a release PR conflicts.

• release-please-protection

  Stop hand edits to release-please files (CHANGELOG, versions) and committed artifacts built from them. Use when editing changelogs, bumping versions, releasing, or feeding a version to generated docs.

• upstream-pr-contribution

  Opening a pull request against a repository you do not own. Use when about to open one, to read CONTRIBUTING.md and the PR template in full and meet the contribution gates bots enforce.

• worktree-stale-base-merge

  Merging a PR from a parallel worktree-agent branch, or any branch cut from an older main. Use when deciding whether a green CI check still means anything after sibling branches have landed.

Subagents (1)

• git-ops

  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. - git-c

Similar plugins