git-publish

Merge develop into main and push both branches to origin.

11|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/dnviti/arsenale --skill git-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-publish
Source: https://github.com/dnviti/arsenale/tree/main/.claude/skills/git-publish
Command: npx skills add https://github.com/dnviti/arsenale --skill git-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates merging develop into main and pushing both branches to the remote, reducing manual cross-branch coordination and drift in a shared repo.

Core Features & Use Cases

  • Automated merge workflow: Check out main, pull latest changes, merge develop, and complete simple conflict resolutions.
  • Dual-branch push: Push both main and develop back to origin to keep remotes synchronized.
  • Safety & predictability: Ensure a clean working tree and provide clear messaging for failures or conflicts.

Quick Start

Run the git-publish operation to merge develop into main and push both branches to origin.

Frequently Asked Questions about git-publish

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

FAQPage Schema
How do I automate merging develop into main and pushing both branches to origin?

Automating the develop to main merge and push requires checking out main, pulling latest changes, merging develop, resolving conflicts, and pushing both branches to origin. This workflow reduces manual cross-branch coordination and keeps remote repositories synchronized.

What is the best way to keep main and develop branches synchronized across remote repositories?

Keeping main and develop synchronized involves pushing both branches back to origin immediately after merging. A dual-branch push ensures the remote repository reflects the latest integration state and prevents drift in shared collaborative environments.

How does conflict resolution work when merging develop into main?

Conflict resolution during the develop to main merge is handled within the automated workflow steps. The process checks out main, pulls latest changes, merges develop, and applies simple conflict resolutions before completing the push to origin.

Do I need a clean working tree before merging develop into main?

Yes, a clean working tree is required before merging develop into main. Ensuring no uncommitted changes provides safety and predictability, allowing the workflow to pull latest changes and push both branches without conflicts.

Can I use this Git merge workflow for collaborative software projects with multiple environments?

Yes, this Git merge workflow applies to standard collaborative software projects with multiple environments. It synchronizes deployments by merging develop into main and pushing both branches to origin, preventing drift across shared repositories.

What happens if the automated Git merge to main fails or encounters conflicts?

When the automated Git merge fails or encounters conflicts beyond simple resolution, the workflow provides clear messaging for the failure. This ensures predictability and prevents incomplete merges from being pushed to the origin.