merge-main

Automate release workflows from pre-flight to tagging for develop-to-main cycles.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/JDenn0514/surveycore --skill merge-main-jdenn0514
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-main
Source: https://github.com/JDenn0514/surveycore/tree/main/.claude/skills/merge-main
Command: npx skills add https://github.com/JDenn0514/surveycore --skill merge-main-jdenn0514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management for Git-based projects is error-prone and time-consuming. This skill provides a guided, end-to-end workflow that ensures NEWS.md and DESCRIPTION are updated correctly, PRs are created, CI is monitored, and releases are tagged, reducing manual toil and governance gaps.

Core Features & Use Cases

  • End-to-end release automation from pre-flight to tagging, with strict guardrails that only allow updates to NEWS.md and DESCRIPTION.
  • Stepwise task tracking: pre-flight checks, NEWS.md drafting, PR creation, CI monitoring, merge, tag, and post-release bumps.
  • Use Case: When preparing a new version, trigger the Merge-Main process to execute release tasks and document changes.

Quick Start

Trigger the Merge-Main release workflow and follow the prompts to complete the release.

Frequently Asked Questions about merge-main

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

FAQPage Schema
How do I automate a git release workflow from develop to main?

To automate a git release workflow from develop to main, this skill guides the end-to-end process including pre-flight checks, version bumps, PR creation, CI monitoring, and tagging. It enforces guardrails by restricting edits to NEWS.md and DESCRIPTION.

What is the best way to coordinate version bumps and PR creation for a release?

The best way to coordinate version bumps and PR creation is using a guided release workflow that tracks each step. This process ensures version bumps and PR creation are executed sequentially with required CI checks before merging.

Can I enforce guardrails to prevent unauthorized code changes during a release?

Yes, you can enforce guardrails during a release by restricting file edits to NEWS.md and DESCRIPTION. This prevents unauthorized code changes and ensures only release metadata is modified throughout the workflow.

How do I monitor CI checks before merging a release PR?

You monitor CI checks before merging a release PR through the workflow's explicit status tracking step. It coordinates CI monitoring across steps to ensure all required checks pass before the merge and tagging proceed.

Does this release workflow support post-release version bumping?

Yes, this release workflow supports post-release version bumping as a final step. After tagging the release, it coordinates the post-release bump to prepare the project repository for the next development cycle.

When do I need an end-to-end release workflow with task tracking?

You need an end-to-end release workflow with task tracking when managing Git-based projects using develop-to-main release cycles. It reduces manual toil and governance gaps by enforcing explicit task creation and traceability across pre-flight, merge, and tagging steps.