push

Stage, commit, and push Git changes with conventional commit messages.

1|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/mpazaryna/agentic-factory --skill push-mpazaryna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/mpazaryna/agentic-factory/tree/main/dev/developer-workflow/skills/push
Command: npx skills add https://github.com/mpazaryna/agentic-factory --skill push-mpazaryna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of staging, committing, and pushing Git changes to a remote repository while enforcing best practices and preventing common errors.

Core Features & Use Cases

  • Guided Staging: Ensures individual files are reviewed and staged intentionally.
  • Conventional Commits: Enforces a structured commit message format for clarity and automation.
  • Safe Pushing: Prevents accidental force-pushes and direct commits to main branches.
  • Conflict Resolution Prompt: Guides users through rebasing if upstream changes conflict.
  • Use Case: After making several code modifications, use this Skill to ensure your changes are committed with a clear, compliant message and pushed to the remote origin without risking data loss or breaking the main branch.

Quick Start

Use the push skill to stage, commit, and push the current branch following git governance rules.

Frequently Asked Questions about push

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

FAQPage Schema
How do I safely commit and push Git changes to a remote repository?

To safely commit and push Git changes, you need to stage individual files, write a conventional commit message, and push to the remote origin. This process prevents accidental force-pushes and blocks direct commits to main branches.

What is the conventional commit format for a Git push workflow?

The conventional commit format for a Git push workflow enforces a structured commit message structure for clarity and automation. It requires individual file staging and specific message formatting to ensure safe push operations without risking data loss.

How do I handle upstream conflicts when pushing code to a remote branch?

To handle upstream conflicts when pushing code to a remote branch, you must resolve them through rebasing. The workflow guides you through the rebase process to safely integrate remote changes before completing the push operation.

Can I force push directly to the main branch using automated Git workflows?

No, you cannot force push directly to the main branch using automated Git workflows. Safe pushing rules explicitly prevent accidental force-pushes and direct commits to main branches to protect remote repository integrity.

Does automated Git staging review individual files before committing?

Yes, automated Git staging reviews individual files before committing. Guided staging ensures each file is reviewed and staged intentionally, enforcing Git governance rules before generating a conventional commit message and pushing.

What is the best way to create a remote branch and push local commits?

The best way to create a remote branch and push local commits is through a guided workflow that handles remote branch creation automatically. It enforces safe push operations and manages upstream rebasing if conflicts arise.