git-pr-ops-core
Coordinates the gated review, preparation, and merge process for GitHub pull requests.
Install
mkdir -p .claude/skills/git-pr-ops-core && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11576" && unzip -o skill.zip -d .claude/skills/git-pr-ops-core && rm skill.zipInstalls to .claude/skills/git-pr-ops-core
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Shared reference for the git-pr-ops cluster: the gated review→prepare→merge pipeline, the `.local/` artifact handoff (review.json findings), head-SHA pinning, the push/merge safety rules (force-with-lease, no auto-merge, never push main), and the finding-severity contract. USE WHEN preparing or merging a GitHub PR, resolving review findings, or wiring the issue→PR flow — the interlocking rules every spoke shares.Key capabilities
- →Enforce a three-gated pipeline for PR review, prepare, and merge
- →Produce `.local/` artifacts for handoff between stages
- →Resolve findings based on severity contract (BLOCKER, IMPORTANT, NIT/MINOR)
- →Ensure push and merge safety rules are followed (e.g., force-with-lease)
- →Perform head-SHA pinned squash merges
- →Generate a changelog as a mandatory part of the workflow
How it works
The skill orchestrates a three-stage pipeline (review, prepare, merge) where each stage produces artifacts consumed by the next, ensuring findings are resolved and safety rules are met before merging.
Inputs & outputs
When to use git-pr-ops-core
- →Resolving PR review findings
- →Preparing a PR for merge
- →Enforcing merge safety rules
About git-pr-ops-core
Enforces a strict 3-stage pipeline (review, prepare, merge) ensuring findings are resolved before merging and commits are pinned to verified SHAs.
Shared reference for the git-pr-ops cluster: the gated review→prepare→merge pipeline, the `.local/` artifact handoff (review.json findings), head-SHA pinning, the push/merge safety rules (force-with-lease, no auto-merge, never push main), and the finding-severity contract. USE WHEN preparing or merg
When not to use it
- →When the user needs to skip any stage of the pipeline
- →When the user needs to push directly to the main branch
- →When the user needs to merge PRs without resolving required findings
Limitations
- →The pipeline stages are ordered and not optional.
- →Prepare pushes only to the PR head, only with `--force-with-lease`.
- →Merge is head-SHA pinned (`--match-head-commit`) to prevent merging unreviewed commits.
How it compares
This skill enforces a strict, artifact-gated pipeline for PR operations, providing a more controlled and auditable merge process than typical manual or less structured workflows.
Compared to similar skills
git-pr-ops-core side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| git-pr-ops-core (this skill) | 0 | 5mo | Caution | Advanced |
| resolve-conflicts | 81 | 12mo | Review | Intermediate |
| dependency-upgrade | 26 | 8mo | Review | Intermediate |
| git-commits | 21 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Sheshiyer
View all by Sheshiyer →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.