git-push

Review pending commits and require explicit approval before executing git push.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/controlaltnerd/arc --skill git-push-controlaltnerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-push
Source: https://github.com/controlaltnerd/arc/tree/main/.github/skills/git-push
Command: npx skills add https://github.com/controlaltnerd/arc --skill git-push-controlaltnerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that no code is pushed to remote repositories without explicit user approval, preventing accidental pushes and providing transparency into what is being committed.

Core Features & Use Cases

  • Commit Review: Presents all pending commits with detailed information (message, files changed) for user review.
  • Branch Awareness: Clearly identifies the current branch and the number of commits to be pushed.
  • User Approval Gate: Requires explicit "yes" or "no" from the user before executing git push.
  • Error Handling: Provides clear feedback on push success, failure, or cancellation, with options for next steps.
  • Use Case: After a day of coding, you have several commits ready. This Skill will show you exactly what you're about to push, allowing you to confirm or cancel before it goes live.

Quick Start

Use the git-push skill to review and approve pending commits for the current branch.

Frequently Asked Questions about git-push

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

FAQPage Schema
How do I review pending git commits before pushing to a remote repository?

To review pending git commits before a remote push, you need a workflow that gathers and presents commit messages and file changes. This approach ensures full awareness of pending modifications before giving explicit approval.

What is the best way to prevent accidental git pushes during version control?

The best way to prevent accidental git pushes is to implement a user approval gate that requires explicit confirmation before executing remote commits. This provides transparency into what is being committed and stops accidental pushes.

Can I see which files are changed in multiple commits before running git push?

Yes, you can see which files are changed in multiple commits before running git push by using a tool that handles multiple commit scenarios. It will gather and present detailed information about all pending changes for your review.

Does the git push approval process handle push failures and cancellations?

Yes, the git push approval process handles push failures and cancellations through clear error handling. It provides feedback on push success, failure, or cancellation, along with options for next steps.

How does branch awareness work when approving remote git commits?

Branch awareness works by clearly identifying the current branch and the exact number of commits to be pushed. This information is presented alongside commit messages and file changes before you approve the remote push.