Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

Apache-2.0Auto-check passedDevelopment

Install Push

skills CLI
$ npx skills add PacificStudio/openase --skill push -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PacificStudio/openase push --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/push .claude/skills/push && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
push
GitHub stars
268
Token cost
~1.2k tokens
SKILL.md length
483 words
Files
2 (incl. scripts)
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

  • Works in 11 steps: Identify the current branch and inspect… → If there are intended but uncommitted… → Ensure origin/main is available locally → …
  • Publish updates
  • SKILL.md covers Prerequisites, Goals, Related Skills and Validation Gate, plus 3 more sections
  • Runs Shell scripts from its folder; calls make, gh and git

What it does

Push is an agent skill from PacificStudio/openase. Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/openase_ci_gate.sh`).

It sits in Development, covering Pull requests. The repository describes itself as: Ticket-Driven Automated Software Engineering. OpenASE is an all-in-one platform that turns tickets into working code — AI agents automatically pick up tickets, execute workflows… The licence is Apache-2.0.

When your agent uses it

  • Publish updates
  • Create a pull request

Example prompts

  • “/push”

Requirements

  • A Bash shell

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Identify the current branch and inspect working tree state.
  2. If there are intended but uncommitted changes, use the commit skill first.
  3. Ensure origin/main is available locally
  4. Run the local CI gate for the current branch diff
  5. Push the branch to origin, setting upstream tracking if needed.
  6. If the push is rejected because the remote moved
  7. If the push fails due to auth, permissions, branch protection, or workflow
  8. Ensure a PR exists for the branch
  9. Write a clear PR title that describes the shipped outcome, not just the last
  10. Write or refresh the PR body explicitly. OpenASE does not currently require a
  11. Reply with the PR URL from gh pr view.

What it can do on your machine

Read from SKILL.md and the folder at commit e530faf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • make
    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Push loads about 1.2k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 483 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from PacificStudio/openase at commit e530faf, republished under its Apache-2.0 licence (© PacificStudio). 483 words, ~1,164 tokens.

Download SKILL.mdSave it as .claude/skills/push/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
push
description
Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

Push

Prerequisites

  • gh CLI is installed and available in PATH.
  • gh auth status succeeds for GitHub operations in this repo.
  • corepack pnpm is available for frontend validation.

Goals

  • Push the current branch to origin safely.
  • Create a PR if none exists for the branch, otherwise update the existing PR.
  • Keep PR metadata aligned with the actual total scope of the branch.
  • Run the same local validation gates that current CI expects before publishing.
  • pull: use this when push is rejected or the branch must be merged with the latest origin/main.
  • commit: use this when there are local changes that are intended to ship but are not committed yet.

Validation Gate

Use the repo-local helper script:

  • .codex/skills/push/scripts/openase_ci_gate.sh

That script mirrors .github/workflows/ci.yml instead of asking the agent to guess which checks are needed:

  • Always runs make openapi-check because CI always runs API contract checks.
  • Detects go_changed and web_changed using the same path rules as CI.
  • Runs frontend CI with make web-install and corepack pnpm --dir web run ci when web_changed=true.
  • Runs backend and Go lint checks with make check, make build, LINT_BASE_REV=<base> make lint, make lint-depguard, and make lint-architecture when go_changed=true.

If the branch scope is ambiguous, use the script anyway; it already biases toward the stricter CI-compatible outcome.

Steps

  1. Identify the current branch and inspect working tree state.
  2. If there are intended but uncommitted changes, use the commit skill first.
  3. Ensure origin/main is available locally:
    • git fetch --no-tags origin main
  4. Run the local CI gate for the current branch diff:
    • .codex/skills/push/scripts/openase_ci_gate.sh
    • Use --plan first if you want to inspect which jobs it will run.
  5. Push the branch to origin, setting upstream tracking if needed.
  6. If the push is rejected because the remote moved:
    • Run the pull skill to merge origin/main and/or remote branch updates.
    • Rerun .codex/skills/push/scripts/openase_ci_gate.sh.
    • Push again.
    • Use --force-with-lease only when local history was intentionally rewritten.
  7. If the push fails due to auth, permissions, branch protection, or workflow restrictions, stop and surface the exact error. Do not rewrite remotes or switch protocols as a workaround.
  8. Ensure a PR exists for the branch:
    • If no PR exists, create one.
    • If a PR exists and is open, update it.
    • If the branch is tied to a closed or merged PR, create a new branch and a new PR instead of reusing stale history.
  9. Write a clear PR title that describes the shipped outcome, not just the last commit.
  10. Write or refresh the PR body explicitly. OpenASE does not currently require a repository PR template, so include concrete sections such as:
Show full SKILL.md (53 more words)Show less
  • Summary
  • Validation
  • Risks / follow-up
  1. Reply with the PR URL from gh pr view.

Commands

sh
# Identify branch
branch=$(git branch --show-current)

# Sync base branch for deterministic validation scope
git fetch --no-tags origin main

# Preview and run the CI-compatible validation gate
.codex/skills/push/scripts/openase_ci_gate.sh --plan
.codex/skills/push/scripts/openase_ci_gate.sh

# Push branch
git push -u origin HEAD

# Only if history was intentionally rewritten
git push --force-with-lease origin HEAD

# Inspect PR state
pr_state=$(gh pr view --json state -q .state 2>/dev/null || true)
if [ "$pr_state" = "MERGED" ] || [ "$pr_state" = "CLOSED" ]; then
  echo "Current branch is tied to a closed PR; create a new branch + PR." >&2
  exit 1
fi

# Create or update PR metadata
pr_title="<clear PR title for the total branch scope>"
tmp_pr_body=$(mktemp)
cat > "$tmp_pr_body" <<'EOF'
## Summary
- <what changed>

## Validation
- <commands run>

## Risks / Follow-up
- <risks or none>
EOF

if [ -z "$pr_state" ]; then
  gh pr create --title "$pr_title" --body-file "$tmp_pr_body"
else
  gh pr edit --title "$pr_title" --body-file "$tmp_pr_body"
fi

rm -f "$tmp_pr_body"
gh pr view --json url -q .url

Notes

  • Do not assume .github/pull_request_template.md exists in this repo.
  • Prefer complete, honest PR metadata over placeholder text.
  • Do not replace the helper script with ad hoc command guessing. If CI changes, update the script and this skill together.

© PacificStudio, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .codex/skills/push of PacificStudio/openase.

  • SKILL.md
  • scripts/openase_ci_gate.sh

Open the folder on GitHubat commit e530faf

Compare with similar skills

Push next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Push compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Push this skillPacificStudio/openase268—~1.2kAutomated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from PacificStudio/openase

All 14 skills in this repo
  • Deploy Coolify Review Env

    PacificStudio/openase

    Create or update a branch-scoped Coolify review environment with one command, and delete it with one command.

    268 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check: notes
  • Deploy Openase

    PacificStudio/openase

    Build and locally redeploy OpenASE from the current branch, including web static assets and the Go binary, then restart the local service and verify health.

    268 GitHub stars~564 tokensUpdated 1 mo ago
    Auto-check: notes
  • Local Bootstrap CLI Auth Debug

    PacificStudio/openase

    Diagnose and repair OpenASE CLI access in local bootstrap mode.

    268 GitHub stars~778 tokensUpdated 1 mo ago
    Auto-check passed
  • Report Issue

    PacificStudio/openase

    Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo).

    268 GitHub stars~631 tokensUpdated 1 mo ago
    Auto-check: notes
  • Auto Harness

    PacificStudio/openase

    Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…

    268 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Openase Platform

    PacificStudio/openase

    Platform operations for tickets, projects, and runtime coordination inside OpenASE.

    268 GitHub stars~6.4k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Push

What does Push do?

Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request. Push is an agent skill from PacificStudio/openase. Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

When should I use Push?

Push fits situations like: publish updates; create a pull request.

How do I install Push in Claude Code?

Run `npx skills add PacificStudio/openase --skill push -a claude-code`. Or copy the skill folder (.codex/skills/push in PacificStudio/openase) into .claude/skills/push in your project. Claude Code loads it when a task matches its description.

How do I install Push in Codex?

Run `npx skills add PacificStudio/openase --skill push -a codex`. Or copy the skill folder (.codex/skills/push in PacificStudio/openase) into .agents/skills/push in your project. Codex loads it when a task matches its description.

Can I use Push in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PacificStudio/openase --skill push -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/push, .gemini/skills/push, .github/skills/push and .opencode/skills/push in your project.

What does Push need to run?

Going by SKILL.md and its folder, Push needs a shell for the scripts in its folder and the command-line tools its instructions call (make, gh and git). Our summary lists: A Bash shell.

Does Push access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Push safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Push use?

Push is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Push use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Push?

Skills that share tags, products or a category with Push: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Push?

PacificStudio (a GitHub organization) maintains it in PacificStudio/openase, which has 268 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 9, 2026.

Source: PacificStudio/openase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.