Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g
npxskills add sickn33/antigravity-awesome-skills--skill git-pr-workflows-git-workflowLoading…
Move completed changes from local review to a verified pull request without bypassing repository policy or branch protection.
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.
Before mutation:
AGENTS.md, contribution guidance, maintainer docs, and relevant nested instructions.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.
Resolve these from the request and repository:
Ask only when a missing choice changes the result materially.
git status --short --branch
git diff --stat
git diff --cached --stat
git branch --show-current
git remote -v
Confirm every file in scope. Stop if staged or dirty files cannot be separated safely.
When subagents are available and authorized, assign independent bounded passes for:
Give each reviewer the raw diff and repository instructions. Keep the main agent responsible for deduplication, severity, edits, and final verification.
Run the repository's targeted checks, then its required pre-PR suite. If a check fails:
Do not weaken gates, hide skipped tests, or treat deterministic failures as flaky.
Fetch the target before committing. If currently on a protected/default branch, create a topic branch before mutation.
git fetch origin <target-branch>
git switch -c <topic-branch> origin/<target-branch>
git status --short --branch
Stage only intended paths and create focused conventional commits according to repository policy. Rebase or update the topic branch when strict required checks demand the latest target; never force a shared branch without explicit authorization.
git push -u origin <topic-branch>
gh pr create --base <target-branch> --head <topic-branch> \
--title "<conventional title>" --body-file <body-file>
The PR body must truthfully include:
Never mark a pending automated review or test as completed.
gh pr view <pr-number> --json headRefOid,baseRefOid,mergeable,mergeStateStatus,url
gh pr checks <pr-number>
Bind review evidence to the current full head SHA. If the head or base changes, discard stale conclusions and rerun affected checks.
Use the repository's guarded merge path. Do not replace required checks, merge queues, exact-SHA attestations, or maintainer commands with a raw merge API. After merge, fetch the target and verify the requested remote, CI, deployment, or release state.
Finish when the PR exists at the intended head, required checks are green or have one exact blocker, review evidence is current, unrelated user work is preserved, and any requested guarded merge or deployment is verified.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).