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

Validate Branch

by ZenUml in ZenUml/web-sequence

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

MITAuto-check passedTesting & QA

Install Validate Branch

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

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

GitHub CLI
$ gh skill install ZenUml/web-sequence validate-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/validate-branch .claude/skills/validate-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
validate-branch
GitHub stars
150
Token cost
~1.1k tokens
SKILL.md length
464 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Check Scope → Choose Checks → Feature spot check (UI / diagram changes) → …
  • The user says validate
  • SKILL.md covers Repo Facts, Workflow and Rules
  • Calls yarn, pnpm and git; reaches staging.zenuml.com

What it does

Validate Branch is an agent skill from ZenUml/web-sequence. Run local validation checks for ZenUML web-sequence before pushing, opening a PR, or merging. Use when the user says "validate", "check branch", "run tests", "preflight", "is this ready", or before submit-branch or ship-branch. Covers Yarn/Vite/Jest/Playwright checks, build/release risk, and spot-check plans for UI/diagram changes (see spot-check skill).

Its SKILL.md is about 1.1k 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 Testing & QA, covering Diagrams, Unit testing and Browser testing. It works with Playwright, Vite, Jest and pnpm. The repository describes itself as: Realtime tool for generating sequence diagrams. The licence is MIT.

When your agent uses it

  • The user says validate
  • Before submit-branch

Example prompts

  • “validate”
  • “check branch”
  • “run tests”
  • “/validate-branch”

Workflow steps

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

  1. Check Scope
  2. Choose Checks
  3. Feature spot check (UI / diagram changes)
  4. Report

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:

    • yarn
    • pnpm
    • git

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • staging.zenuml.com

    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

Validate Branch loads about 1.1k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 464 words of instructions outside code blocks.

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

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). 464 words, ~1,052 tokens.

Download SKILL.mdSave it as .claude/skills/validate-branch/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
validate-branch
description
Run local validation checks for ZenUML web-sequence before pushing, opening a PR, or merging. Use when the user says "validate", "check branch", "run tests", "preflight", "is this ready", or before submit-branch or ship-branch. Covers Yarn/Vite/Jest/Playwright checks, build/release risk, and spot-check plans for UI/diagram changes (see spot-check skill).

Validate Branch

Verify the current branch is locally sane before it reaches GitHub Actions.

Repo Facts

  • Repository: ZenUml/web-sequence
  • Base branch: master
  • Package manager for local development: Yarn (yarn install, yarn dev, yarn build)
  • CI currently uses pnpm in GitHub Actions, so note any Yarn/pnpm divergence instead of hiding it.
  • App dev server is Vite on http://127.0.0.1:3000 (Playwright can auto-start via pnpm dev).

Workflow

1. Check Scope

Run:

bash
git status --short --branch
git diff --name-only master...HEAD

If the worktree has unrelated local changes, do not stage or revert them. Validate the current branch changes and mention the unrelated files in the report.

2. Choose Checks

Run the smallest set that gives real confidence:

  • Always: yarn build
  • Unit-test changes or shared logic: yarn test
  • UI behavior changes: start yarn dev, test the changed flow in browser, and run yarn test:e2e when the smoke suite is relevant.
  • Release/extension changes: yarn release after yarn build
  • Firebase/functions changes: inspect functions/package.json and run the relevant functions build/test/deploy dry-run command if available.
  • Lint-sensitive changes: yarn lint, but if local ESLint is blocked by missing eslint-config-synacor, report that as an environment/config blocker and continue with other checks.

Do not run expensive or stateful deploy commands unless the user explicitly asks.

3. Feature spot check (UI / diagram changes)

When to skip: docs-only, CI/workflow-only, unrelated skill files.

For changes under src/components, src/style.css, src/assets/tailwind.css, vite.config.js, e2e/, or @zenuml/core integration:

3a. Write a spot check plan first

Use the spot-check skill — write the plan (behavior, target URL, assertions, method) before touching the browser or Playwright.

3b. Choose how to test
SituationTarget
Branch not deployed yetyarn dev → http://127.0.0.1:3000
Validating staging deployPW_BASE_URL=https://staging.zenuml.com + Playwright
@zenuml/core / preview iframeAssert inside #demo-frame (see spot-check skill)
Broad DSL/renderer regressionRun e2e/tests/dsl-spot-check.spec.js as a recipe (optional)
Show full SKILL.md (182 more words)Show less
3c. Execute the plan

Follow the spot-check skill workflow. Prefer Playwright CLI for repeatability; use browser MCP for ad-hoc steps.

For each [ ] assertion: interact → observe signal → screenshot diagram/preview when visual proof matters.

If every assertion passes: Step 3 PASS. If any fails: FAIL — include which assertion failed and evidence path; fix code, then re-run from §2.

Common gotchas: see spot-check skill (iframe scope, loginAndsaveMessageSeen, third-party console noise). Branch-specific:

  • Dev vs CI package manager: local yarn build, CI pnpm build — run pnpm build if the change touches lockfile or Vite resolution.
  • Empty preview canvas with passing text poll: capture render-diagram-* screenshot; layout/CSS regressions need visual evidence.
4. Report

Use this shape:

text
Validation: PASS|FAIL|PARTIAL
- Build: ...
- Tests: ...
- Browser smoke: ...
- Skipped: ... (reason)
- Unrelated local changes: ...

FAIL means a required check failed. PARTIAL means useful checks passed but one check could not run because of environment, credentials, missing config, or an intentionally skipped scope.

Rules

  • Never mark validation PASS if a required check was skipped or blocked.
  • Never clean, revert, or stage unrelated local files.
  • Prefer fixing reproducible local failures before suggesting CI retry.
  • Preserve the exact failing command and the important error lines in the final report.

© 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/validate-branch of ZenUml/web-sequence.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e38bd91

Compare with similar skills

Validate 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.

Validate Branch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Validate Branch this skillZenUml/web-sequence150—~1.1kAutomated safety check: PassMIT
Ckeditor5 TestingTriliumNext/Trilium38k—~3.3kAutomated safety check: PassAGPL-3.0
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone
Ha Frontend Testinghome-assistant/frontend5.7k—~1.7kAutomated safety check: PassApache-2.0
Playwright Testingchongdashu/vibejam-starter-pack149—~2.2kAutomated safety check: PassNone
Testingradix-ng/primitives274—~3.3kAutomated safety check: PassMIT

Similar skills

  • Ckeditor5 Testing

    TriliumNext/Trilium

    Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.

    38k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Ha Frontend Testing

    home-assistant/frontend

    Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.

    5.7k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Testing

    radix-ng/primitives

    Test Radix NG primitives across every layer and pick the RIGHT one for a change: Vitest unit (zoneless), jest-axe a11y, Playwright browser regression (apps/visual-regression), SSR…

    274 GitHub stars~3.3k tokensUpdated 10 days ago
    Testing & QAAuto-check passed

  • Menu Testing Ssr

    asmyshlyaev177/react-horizontal-scrolling-menu

    Server rendering and testing for react-horizontal-scrolling-menu: the library is client-only ('use client' required in React Server Components, else "createContext is not a function"), SSR first…

    790 GitHub stars~3.5k tokensUpdated 7 days ago
    Testing & QAAuto-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

  • Submit Branch

    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.

    150 GitHub stars~765 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 Validate Branch

What does Validate Branch do?

Run local validation checks for ZenUML web-sequence before pushing, opening a PR, or merging. Validate Branch is an agent skill from ZenUml/web-sequence. Run local validation checks for ZenUML web-sequence before pushing, opening a PR, or merging.

When should I use Validate Branch?

Validate Branch fits situations like: the user says validate; before submit-branch.

How do I install Validate Branch in Claude Code?

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

How do I install Validate Branch in Codex?

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

Can I use Validate 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 validate-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/validate-branch, .gemini/skills/validate-branch, .github/skills/validate-branch and .opencode/skills/validate-branch in your project.

What does Validate Branch need to run?

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

Does Validate Branch access the network?

SKILL.md names 1 domain. In commands or code: staging.zenuml.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

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

About 1.1k tokens (SKILL.md is roughly 4.2k 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 Validate Branch?

Skills that share tags, products or a category with Validate Branch: Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), Ha Frontend Testing (home-assistant/frontend, 5.7k stars) and Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Validate 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.