Agent skill · software engineering · sickn33
git-pr-workflows-git-workflow
Orchestrate review, tests, commits, branch pushes, and pull-request creation with parallel agents. Use when completed changes must move through validation into a PR or guarded merge.
Why this skill is useful
Adds specific git commands and workflows for managing pull requests and repository policies that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Guarded Git Pull Request Workflow Move completed changes from local review to a verified pull request without bypassing repository policy or branch protection. When to Use Use for completed implementation work that must be reviewed, tested, committed, pushed to a topic branch, and opened as a pull request. Use the repository's dedicated maintainer or release workflow instead when one is mandatory. Policy Gate Before mutation: 1. Read AGENTS.md, contribution guidance, maintainer docs, and relevant nested instructions. 2. Inspect the current branch, worktree, remotes, upstream, and effective target-branch protection. 3. Discover repository-native validation, commit, PR, merge, and release commands. 4. Preserve unrelated dirty and staged files. Repository policy wins over flags and user shorthand. Trunk-based development does not imply a direct push: when the target is protected, use a short-lived branch and pull request. If a repository defines a mandatory maintainer skill or guarded merge command, hand off merge and release actions to it. In agentic-awesome-skills, use antigravity-maintainer-batch-release and npm run merge:batch. Inputs Resolve these from the request and repository: target branch, defaulting to the repository default branch; intended changed files and excluded user work; required test, lint, security, build, and documentation checks; branch naming and commit-message conventions; draft or ready-for-review PR state; required reviewers, labels, issue links, and merge method. Ask only when a missing choice changes the result materially. Workflow 1. Capture the exact change Confirm every file in scope. Stop if staged or dirty files cannot be separated safely. 2. Review in parallel When subagents are available and authorized, assign independent bounded passes for: correctness and regression risk; security, secrets, permissions, and dependency risk; test coverage and repository-policy compliance. Give each reviewer the raw diff and repository instructions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/git-pr-workflows-git-workflow--3c58b3