push

Synchronize a local branch with a fork and draft a PR against upstream main.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Arry8/openclaw-edge --skill push-arry8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/Arry8/openclaw-edge/tree/main/.codex/skills/push
Command: npx skills add https://github.com/Arry8/openclaw-edge --skill push-arry8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs the current feature branch with the user's fork and automatically drafts a PR against the upstream repository openclaw/openclaw main, enabling safe collaboration workflows without manual PR orchestration.

Core Features & Use Cases

  • Safely push the current branch to the fork origin without using force push.
  • Create or update a draft PR against openclaw/openclaw:main, with PR template usage and branch-aware title handling.
  • Preserve human edits by merging in PR content while sanitizing dynamically captured prompts.

Quick Start

Push the current branch to your fork and open a draft PR against openclaw/openclaw:main using the built-in template and safety checks.

Frequently Asked Questions about push

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

FAQPage Schema
How do I push a local feature branch to a fork and draft an upstream pull request?

To push a local feature branch to a fork and draft an upstream pull request, synchronize your branch with origin and automatically generate a draft PR against the upstream main branch using built-in safety checks and PR templates.

What is the safest way to sync a fork-based workflow branch before opening a pull request?

The safest way to sync a fork-based workflow branch is to enforce a clean working tree, avoid force pushes, and align the feature branch with both origin and upstream repositories deterministically before drafting a PR.

How do I create a draft PR against an upstream repository without losing manual edits to the PR body?

Create a draft PR against an upstream repository by merging dynamically captured prompts while preserving manual edits to the PR body, applying deterministic rules and hashes to ensure human content remains intact during branch synchronization.

Does this branch management workflow require a clean working tree for pull request generation?

Yes, this branch management workflow requires a clean working tree for pull request generation to guarantee safe synchronization and prevent accidental overwrites when pushing the feature branch to the fork origin.

Why does my pull request template change when pushing to an upstream fork?

Your pull request template may change because the workflow sanitizes dynamically captured prompts and applies branch-aware title handling to standardize the PR body against the upstream main repository.

Can I use force push when aligning my feature branch with an upstream fork?

No, you cannot use force push when aligning your feature branch with an upstream fork, as the workflow enforces strict safety constraints to prevent destructive updates and protect the upstream pull request history.