ankyr-ci-push

Enforces consent, PR-tier review, and unresolved-thread checks before pushing to a remote git branch.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-ci-push-guyerreich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ankyr-ci-push
Source: https://github.com/GuyErreich/AI_Agents/tree/main/plugins/ankyr-git/skills/ankyr-ci-push
Command: npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-ci-push-guyerreich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents accidental or unreviewed pushes by gating every git push behind explicit user consent, a clean PR-tier code review, and a check for unresolved review threads on any open pull request. ## Core Features & Use Cases - Explicit Push Consent: Refuses to push unless the user explicitly requests it, with a scoped-consent exception for approved pr-resolver fix commits. - PR-Tier Review Gate: Runs the project reviewer or the ankyr-review plugin's reviewer skill and requires a clean verdict or an explicit skip before pushing. - Open PR Handoff: Uses gh pr view to detect an open PR on the current branch and hands off to the pr-resolver when unresolved review threads exist instead of pushing on top. - Use Case: A developer finishes a feature branch and asks to push; the workflow confirms consent, runs the review, finds an open PR with unresolved comments, and routes to the resolver rather than stacking new commits. ## Quick Start Ask the agent to push the current branch and it will verify consent, review status, and open PR threads before running git push.

Frequently Asked Questions about ankyr-ci-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push a git branch safely after code review?▼

Request an explicit push and the workflow first runs a PR-tier review, then checks for an open PR with gh pr view. It only runs git push after consent is confirmed, the review verdict is clean or explicitly skipped, and no unresolved review threads remain.

What happens when I push a branch with an open pull request?▼

The workflow fetches the PR's review threads and, if any are unresolved, stops and hands off to the pr-resolver instead of pushing. This avoids stacking unrelated commits on top of pending review feedback.

Can the pr-resolver push commits without a separate push request?▼

Yes, approving the resolver plan or explicitly asking to resolve comments grants scoped commit and push consent for approved fix commits only. This exception applies solely during an active pr-resolver fix plan after validation.

Does this workflow allow force-pushing to shared branches?▼

Force-pushing to a shared branch is never done without an explicit user request. The workflow also warns before any force-push to a protected branch, keeping destructive history rewrites under direct user control.

Why does the push stop even after my local review passed?▼

The push halts when an open PR on the current branch has unresolved review threads, because pushing unrelated changes on top would mix concerns. Resolve the threads through the pr-resolver first, then push.