publish

Push the current git branch to origin with optional draft PR and Codex review.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill publish-kord96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/Kord96/kordinate/tree/main/shared/skills/publish
Command: npx skills add https://github.com/Kord96/kordinate --skill publish-kord96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental updates to main while making it easy to publish feature branches and optionally prepare them for review, ensuring teams don't accidentally mutate the protected main branch during everyday pushes.

Core Features & Use Cases

  • Safe publishing: Always fetches first, shows branch state, and refuses to run on main to prevent accidental merges or updates.
  • Workspace validation: Detects dirty working trees and requires a clean state before pushing.
  • Optional review flow: Pushes the current branch to origin and can optionally prepare or create a draft pull request and include a Codex review request when requested.
  • Use Case: A developer finishing a feature uses this Skill to verify branch status, push the branch, and open a draft PR requesting a technical review without touching main.

Quick Start

Publish the current branch to origin and optionally create a draft pull request requesting Codex review by including the --draft-pr and --codex-review flags.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I push a git branch to origin without accidentally modifying main?

To push a git branch without modifying main, use a safe publishing workflow that fetches origin first, verifies the current branch is not main, and pushes only the local feature branch to the remote repository.

Can I create a draft pull request and request a Codex review directly from the command line?

Yes, you can create a draft pull request and request a Codex review by running a branch publish command with the --draft-pr and --codex-review flags after pushing your local feature branch to origin.

Why does my git workflow refuse to push when the working tree is dirty?

A git workflow refuses to push when the working tree is dirty to ensure workspace validation; it requires a clean state before pushing a branch to origin to prevent uncommitted changes from causing merge conflicts.

What's the best way to check if my local branch is ahead or behind origin before pushing?

The best way to check if a branch is ahead or behind origin is to perform a git fetch before pushing; this determines the branch status and ensures you only publish a clean feature branch.

Does this branch publishing workflow prevent accidental updates to the main branch?

Yes, this branch publishing workflow prevents accidental updates to main by explicitly refusing to operate on the main branch, ensuring teams don't accidentally mutate the protected main branch during everyday pushes.

When should I use a draft PR workflow instead of pushing directly to main?

You should use a draft PR workflow instead of pushing to main when finishing a feature, allowing you to push the branch to origin and open a draft PR requesting technical review without touching the protected main branch.