release

Name: release
Availability: InStock
Author: tachiiri-org

Create a pull request from the dev branch to main after verifying branch and remote state.

Updated Feb 28, 2026

Search Tags:#git #workflow #devops #pull request #branching #release

Ready to run

npx skills add https://github.com/tachiiri-org/agent-ops --skill release-tachiiri-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/tachiiri-org/agent-ops/tree/main/.codex/skills/release
Command: npx skills add https://github.com/tachiiri-org/agent-ops --skill release-tachiiri-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the crucial step of ensuring a release pull request is open from the development branch to the main branch, streamlining the release process and preventing accidental direct merges.

Core Features & Use Cases

Branch Verification: Automatically checks if the current branch is dev and switches to it if necessary.
Remote Sync: Ensures the dev branch is up-to-date with the remote repository.
PR Management: Verifies the existence of an open PR from dev to main, creating one if it doesn't exist.
Use Case: Before deploying new features, this Skill guarantees that the release candidate is properly staged in a PR, allowing for review and preventing direct commits to the production branch.

Quick Start

Use the release skill to ensure there is an open pull request from dev to main.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate creating a release pull request from dev to main?▼

Automating a release pull request from dev to main requires verifying the current branch, pushing updates to the remote repository, and automatically creating the PR if one does not already exist.

How does branching verification work when preparing a release PR?▼

Branching verification checks if the current branch is dev and switches to it if necessary, ensuring the release pull request is correctly staged from the development branch to the main branch.

What's the best way to prevent accidental direct merges to the main branch?▼

Preventing accidental direct merges to the main branch is achieved by ensuring an open pull request exists from dev to main, forcing code to be reviewed before production deployment.

How do I sync the dev branch with the remote repository before opening a PR?▼

Syncing the dev branch with the remote repository requires pushing local changes to the remote before verifying or creating a pull request targeting the main branch.

Do I need to manually check for an existing pull request before deploying?▼

Manually checking for an existing pull request before deploying is unnecessary, as this process automatically verifies if an open PR from dev to main exists and creates one if it is missing.

When should I use an automated release PR workflow?▼

Use an automated release PR workflow before deploying new features to guarantee the release candidate is properly staged for review, preventing direct commits to the production branch.