Agent skill

Push

by sushaantu in sushaantu/boxento

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

MITAuto-check passedDevelopment

Install Push

skills CLI
$ npx skills add sushaantu/boxento --skill push -a claude-code

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

GitHub CLI
$ gh skill install sushaantu/boxento 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/sushaantu/boxento.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
154
Token cost
~613 tokens
SKILL.md length
265 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 8 steps: Identify the current branch and confirm… → Run the required validation for the scope. → Push the branch to origin with upstream… → …
  • Publish updates
  • SKILL.md covers Prerequisites, Goals, Related skills and Validation gate, plus 3 more sections
  • Calls gh, bun and git

What it does

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

Its SKILL.md is about 610 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: Open-source customizable start page. The licence is MIT.

When your agent uses it

  • Publish updates
  • Create a pull request

Example prompts

  • “/push”

Workflow steps

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

  1. Identify the current branch and confirm the remote state.
  2. Run the required validation for the scope.
  3. Push the branch to origin with upstream tracking if needed.
  4. If push is rejected because the remote moved, run the pull skill, rerun validation, and push again.
  5. If push fails because of auth, permissions, or repo rules, stop and surface the exact error.
  6. Ensure a PR exists for the branch
  7. Write or update a clear PR title and body that match the current diff.
  8. 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 3209676. 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

    Shell commands in SKILL.md call:

    • gh
    • bun
    • git
    • bunx

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

  • Network

    No URLs in SKILL.md. Its commands use gh, git and bunx, 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 613 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 265 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from sushaantu/boxento at commit 3209676, republished under its MIT licence (© sushaantu). 265 words, ~613 tokens.

Download SKILL.mdSave it as .claude/skills/push/SKILL.md (or your agent's skills folder).
name
push
description
Push current branch changes to origin and create or update the corresponding pull request; 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.

Goals

  • Push current branch changes to origin safely.
  • Create a PR if none exists for the branch, otherwise update the existing PR.
  • Keep branch history clean when remote has moved.
  • pull: use this when push is rejected or the branch is stale.

Validation gate

Run the checks that match the repo's normal contribution flow before pushing:

sh
bun run lint
bun run test

Run browser coverage too when the change is user-facing, routing-related, or otherwise browser-observable:

sh
bun run test:e2e

If Playwright browsers are missing, install them first:

sh
bunx playwright install --with-deps chromium

Steps

  1. Identify the current branch and confirm the remote state.
  2. Run the required validation for the scope.
  3. Push the branch to origin with upstream tracking if needed.
  4. If push is rejected because the remote moved, run the pull skill, rerun validation, and push again.
  5. If push fails because of auth, permissions, or repo rules, stop and surface the exact error.
  6. Ensure a PR exists for the branch:
    • If no PR exists, create one.
    • If a PR exists and is open, update it.
    • If the current branch is tied to a closed or merged PR, create a fresh branch and PR.
  7. Write or update a clear PR title and body that match the current diff.
  8. Reply with the PR URL from gh pr view.

Commands

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

git push -u origin HEAD

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

pr_title="<clear PR title written for this change>"
if [ -z "$pr_state" ]; then
  gh pr create --fill --title "$pr_title"
else
  gh pr edit --title "$pr_title"
fi

gh pr view --json url -q .url

Notes

  • Do not use --force; use --force-with-lease only when local history was intentionally rewritten.
  • Distinguish sync problems from auth or permission problems. Use the pull skill for the former and surface the latter directly.

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

Files

Just SKILL.md in .codex/skills/push of sushaantu/boxento.

Open the folder on GitHubat commit 3209676

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 skillsushaantu/boxento154—~613Automated safety check: PassMIT
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-Anything86k1 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.

    86k 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 sushaantu/boxento

  • Commit

    sushaantu/boxento

    Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

    154 GitHub starsUsed in 2 repos~473 tokens
    Auto-check passed
  • Land

    sushaantu/boxento

    Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

    154 GitHub starsUsed in 1 repo~524 tokens
    Auto-check passed
  • Linear

    sushaantu/boxento

    Use Symphony's lineargraphql client tool for raw Linear GraphQL operations such as comment editing and status updates.

    154 GitHub stars~447 tokensUpdated today
    Auto-check passed
  • Pull

    sushaantu/boxento

    Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch).

    154 GitHub stars~445 tokensUpdated today
    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; use when asked to push, publish updates, or create a pull request. Push is an agent skill from sushaantu/boxento. Push current branch changes to origin and create or update the corresponding pull request; 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 sushaantu/boxento --skill push -a claude-code`. Or copy the skill folder (.codex/skills/push in sushaantu/boxento) 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 sushaantu/boxento --skill push -a codex`. Or copy the skill folder (.codex/skills/push in sushaantu/boxento) 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 sushaantu/boxento --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 the command-line tools its instructions call (gh, bun, git and bunx).

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. Review the folder before installing.

What licence does Push use?

Push is published under the MIT 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 613 tokens (SKILL.md is roughly 2.5k 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, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Push?

sushaantu (a GitHub user) maintains it in sushaantu/boxento, which has 154 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

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