New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Submit Branch

by ZenUml in ZenUml/web-sequence

Push the current ZenUML web-sequence branch, create or reuse a GitHub PR against master, then always run babysit-pr until CI is green or blocked.

MITAuto-check passedDevelopment

Install Submit Branch

skills CLI
$ npx skills add ZenUml/web-sequence --skill submit-branch -a claude-code

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

GitHub CLI
$ gh skill install ZenUml/web-sequence submit-branch --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/ZenUml/web-sequence.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/submit-branch .claude/skills/submit-branch && 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
submit-branch
GitHub stars
150
Token cost
~765 tokens
SKILL.md length
314 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Push the current ZenUML web-sequence branch, create or reuse a GitHub PR against master, then always run babysit-pr until CI is green or blocked.

  • Works in 4 steps: Commit Scoped Changes If Needed → Push The Branch → Reuse Or Create PR → …
  • The user says submit
  • SKILL.md covers Flow, Preconditions, Steps and PR Body Guidance, plus 2 more sections
  • Calls git and gh

What it does

Submit Branch is an agent skill from ZenUml/web-sequence. Push the current ZenUML web-sequence branch, create or reuse a GitHub PR against master, then always run babysit-pr until CI is green or blocked. Use when the user says "submit", "create PR", "open a pull request", "push and PR", or wants to publish branch work without merging. Does not merge — use land-pr after babysit passes.

Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests and Diagrams. It works with GitHub. The repository describes itself as: Realtime tool for generating sequence diagrams. The licence is MIT.

When your agent uses it

  • The user says submit
  • Open a pull request
  • Wants to publish branch work without merging

Example prompts

  • “submit”
  • “create PR”
  • “open a pull request”
  • “/submit-branch”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Commit Scoped Changes If Needed
  2. Push The Branch
  3. Reuse Or Create PR
  4. Babysit CI (mandatory)

What it can do on your machine

Read from SKILL.md and the folder at commit e38bd91. 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:

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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

Submit Branch loads about 765 tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 314 words of instructions outside code blocks.

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

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 ZenUml/web-sequence at commit e38bd91, republished under its MIT licence (© ZenUml). 314 words, ~765 tokens.

Download SKILL.mdSave it as .claude/skills/submit-branch/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
submit-branch
description
Push the current ZenUML web-sequence branch, create or reuse a GitHub PR against master, then always run babysit-pr until CI is green or blocked. Use when the user says "submit", "create PR", "open a pull request", "push and PR", or wants to publish branch work without merging. Does not merge — use land-pr after babysit passes.

Submit Branch

Publish the current branch as a PR for ZenUml/web-sequence, then always babysit CI on that PR.

Flow

text
commit (if needed) → push → create or reuse PR → babysit-pr

Stop at the first failing step. Do not merge.

Preconditions

Run:

bash
git status --short --branch
git remote -v

Only proceed when modified files are clearly in scope for the branch. If the worktree mixes unrelated changes, ask which files to include. Never auto-commit unrelated files.

Steps

1. Commit Scoped Changes If Needed

If there are scoped uncommitted changes, stage only those files and commit with a concise message:

bash
git add <specific-files>
git commit -m "<type>: <summary>"

Do not amend or force-push unless the user explicitly asks.

2. Push The Branch
bash
git branch --show-current
git push -u origin <branch>

If push is rejected, stop and report the reason. Do not force-push.

3. Reuse Or Create PR

Check for an existing PR:

bash
gh pr view --json number,title,url,state,isDraft,headRefName

If no PR exists, create one against master:

bash
gh pr create --base master --title "<concise title>" --body "$(cat <<'EOF'
## Summary
- ...

## Test plan
- ...
EOF
)"

If a PR already exists, note its number and URL — do not create a duplicate.

Use Draft only if the user asks or if the branch is intentionally not ready. This repo does not have a documented draft gate that skips expensive PR E2E.

4. Babysit CI (mandatory)

Always invoke the babysit-pr skill on the PR from Step 3 (new or reused).

  • Pass the PR number explicitly if you have it.
  • Let babysit watch Deploy to Stage, diagnose failures, fix code-caused issues (up to its retry budget), and report final status.
  • If babysit ends FAILED or BLOCKED, stop here — do not merge. Tell the user what failed and whether a fix was pushed.
  • If babysit ends PASSED or checks are still PENDING with babysit still watching, report that state; do not call land-pr unless the user asked to ship/merge.

PR Body Guidance

Mention:

  • User-facing behavior changed
  • Build/config/deploy files changed
  • Validation actually run
  • Known skipped checks or environment blockers

Output

Report:

text
Submitted: PR #<number> <url>
Branch: <branch>
Base: master
Validation included: <yes/no, summary>
Babysit: PASSED|FAILED|PENDING|BLOCKED — <summary>
Notes: <draft state, skipped checks, unrelated local files>

Does Not

  • Run full validation by default; use validate-branch before submit when the branch needs local preflight.
  • Merge; use land-pr after babysit is green and the user wants to land.

© ZenUml, MIT. 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 in .claude/skills/submit-branch of ZenUml/web-sequence.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e38bd91

Compare with similar skills

Submit Branch 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.

Submit Branch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Submit Branch this skillZenUml/web-sequence150—~765Automated safety check: PassMIT
Visual Reviewai-dynamo/dynamo8.2k—~4.5kAutomated safety check: PassApache-2.0
CodeScope Codebase Graph AnalysisQwenLM/qwen-code28k1 repos~9.3kAutomated safety check: PassApache-2.0
Update PRtobihagemann/turbo407—~2.5kAutomated 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

Similar skills

  • Visual Review

    ai-dynamo/dynamo

    Create self-contained interactive HTML code-review dashboards from GitHub or GitLab pull requests, checked-out branch diffs, or supplied unified diffs, with correctness and safe-to-merge scores…

    8.2k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

  • CodeScope Codebase Graph Analysis

    QwenLM/qwen-code

    Answers questions about code structure, history, bugs and PR risk using a CodeScope knowledge graph and semantic index built from the repository.

    28k GitHub starsUsed in 1 repo~9.3k tokens
    DevelopmentAuto-check passed

  • Update PR

    tobihagemann/turbo

    Update an existing GitHub pull request's title and description to reflect the current state of the branch.

    407 GitHub stars~2.5k tokensUpdated yesterday
    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

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

More from ZenUml/web-sequence

  • Babysit PR

    ZenUml/web-sequence

    Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.

    150 GitHub stars~871 tokensUpdated 3 days ago
    Auto-check passed

  • Land PR

    ZenUml/web-sequence

    Merge a green ZenUML web-sequence PR into master and verify staging CI after merge.

    150 GitHub stars~632 tokensUpdated 3 days ago
    Auto-check passed

  • Release App

    ZenUml/web-sequence

    Release ZenUML web-sequence to production (app.zenuml.com) by publishing a GitHub release, wait for deploy-prod CI + @smoke, then run a release-delta spot check (spot-check skill Step 5.5).

    150 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Spot Check

    ZenUml/web-sequence

    Ad hoc, AI-driven verification of a specific behavior on ZenUML web-sequence — not a new checked-in E2E test.

    150 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Validate Branch

    ZenUml/web-sequence

    Run local validation checks for ZenUML web-sequence before pushing, opening a PR, or merging.

    150 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Ship Branch

    ZenUml/web-sequence

    Take the current ZenUML web-sequence branch from local validation through PR submission, green CI, and merge to master.

    150 GitHub stars~456 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Submit Branch

What does Submit Branch do?

Push the current ZenUML web-sequence branch, create or reuse a GitHub PR against master, then always run babysit-pr until CI is green or blocked. Submit Branch is an agent skill from ZenUml/web-sequence. Push the current ZenUML web-sequence branch, create or reuse a GitHub PR against master, then always run babysit-pr until CI is green or blocked.

When should I use Submit Branch?

Submit Branch fits situations like: the user says submit; open a pull request; wants to publish branch work without merging.

How do I install Submit Branch in Claude Code?

Run `npx skills add ZenUml/web-sequence --skill submit-branch -a claude-code`. Or copy the skill folder (.claude/skills/submit-branch in ZenUml/web-sequence) into .claude/skills/submit-branch in your project. Claude Code loads it when a task matches its description.

How do I install Submit Branch in Codex?

Run `npx skills add ZenUml/web-sequence --skill submit-branch -a codex`. Or copy the skill folder (.claude/skills/submit-branch in ZenUml/web-sequence) into .agents/skills/submit-branch in your project. Codex loads it when a task matches its description.

Can I use Submit Branch 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 ZenUml/web-sequence --skill submit-branch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/submit-branch, .gemini/skills/submit-branch, .github/skills/submit-branch and .opencode/skills/submit-branch in your project.

What does Submit Branch need to run?

Going by SKILL.md and its folder, Submit Branch needs the command-line tools its instructions call (git and gh).

Does Submit Branch access the network?

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

Is Submit Branch 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 Submit Branch use?

Submit Branch 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 Submit Branch use?

About 765 tokens (SKILL.md is roughly 3.1k 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 Submit Branch?

Skills that share tags, products or a category with Submit Branch: Visual Review (ai-dynamo/dynamo, 8.2k stars), CodeScope Codebase Graph Analysis (QwenLM/qwen-code, 28k stars), Update PR (tobihagemann/turbo, 407 stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Submit Branch?

ZenUml (a GitHub organization) maintains it in ZenUml/web-sequence, which has 150 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

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