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…
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).
Install Release App
$ npx skills add ZenUml/web-sequence --skill release-app -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZenUml/web-sequence release-app --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ZenUml/web-sequence.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-app .claude/skills/release-app && rm -rf skills-srcUse ~/.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/
Install the "release-app" agent skill from https://github.com/ZenUml/web-sequence/tree/master/.claude/skills/release-app into .claude/skills/release-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-app", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ZenUml/web-sequence/tree/master/.claude/skills/release-appType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ZenUml/web-sequence --skill release-app -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZenUml/web-sequence release-app --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZenUml/web-sequence.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-app .agents/skills/release-app && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-app" agent skill from https://github.com/ZenUml/web-sequence/tree/master/.claude/skills/release-app into .agents/skills/release-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-app", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZenUml/web-sequence --skill release-app -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZenUml/web-sequence release-app --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZenUml/web-sequence.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-app .cursor/skills/release-app && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-app" agent skill from https://github.com/ZenUml/web-sequence/tree/master/.claude/skills/release-app into .cursor/skills/release-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-app", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ZenUml/web-sequence.git --path .claude/skills/release-app--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ZenUml/web-sequence --skill release-app -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZenUml/web-sequence release-app --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZenUml/web-sequence.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-app .gemini/skills/release-app && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-app" agent skill from https://github.com/ZenUml/web-sequence/tree/master/.claude/skills/release-app into .gemini/skills/release-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-app", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ZenUml/web-sequence release-appInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ZenUml/web-sequence --skill release-app -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ZenUml/web-sequence.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-app .github/skills/release-app && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-app" agent skill from https://github.com/ZenUml/web-sequence/tree/master/.claude/skills/release-app into .github/skills/release-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-app", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZenUml/web-sequence --skill release-app -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ZenUml/web-sequence release-app --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZenUml/web-sequence.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-app .opencode/skills/release-app && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-app" agent skill from https://github.com/ZenUml/web-sequence/tree/master/.claude/skills/release-app into .opencode/skills/release-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-app", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-app- GitHub stars
- 150
- Token cost
- ~1.7k tokens
- SKILL.md length
- 669 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
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).
- Works in 6 steps: Confirm master is releasable → Check local HEAD is pushed → Determine the tag name → …
- The user says release
- SKILL.md covers Repo Facts, Pre-flight, Create the Release and Monitor CI, plus 3 more sections
- Calls git, gh and pnpm
What it does
Release App is an agent skill from 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). Use when the user says "release", "release app", "deploy to prod", "ship to production", or invokes /release-app. Does not merge PRs — use ship-branch first if there are pending changes on a feature branch.
Its SKILL.md is about 1.7k 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 Diagrams. It works with GitHub and Chrome Extensions. The repository describes itself as: Realtime tool for generating sequence diagrams. The licence is MIT.
When your agent uses it
- The user says release
- Ship to production
- Invokes /release-app
Example prompts
- “release”
- “release app”
- “deploy to prod”
- “/release-app”
Requirements
- Node.js
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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:
gitghpnpmnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh, pnpm and npm, 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
Release App loads about 1.7k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 669 words of instructions outside code blocks.
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). 669 words, ~1,669 tokens.
Download SKILL.mdSave it as
.claude/skills/release-app/SKILL.md (or your agent's skills folder).- name
- release-app
- description
- 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). Use when the user says "release", "release app", "deploy to prod", "ship to production", or invokes /release-app. Does not merge PRs — use ship-branch first if there are pending changes on a feature branch.
Release App
Deploy the current master to https://app.zenuml.com by publishing a GitHub release, which triggers the Deploy to Prod CI workflow.
Repo Facts
- Repository:
ZenUml/web-sequence - Production URL: https://app.zenuml.com
- Deploy trigger: GitHub Release published (
on: release: types: [published]) - Workflow file:
.github/workflows/deploy-prod.yml - Tag convention:
v<YYYYMMDD>-<short-slug>(e.g.v20260604-core-bump) - Package manager (CI): pnpm
- Package manager (local): Yarn
Pre-flight
1. Confirm master is releasable
git fetch origin
git log --oneline v$(git tag --sort=-version:refname | head -1)..origin/masterShow the user the unreleased commits. If there are zero commits since the last tag, confirm with the user before proceeding — a no-op release is usually unintentional.
2. Check local HEAD is pushed
git log --oneline origin/master..HEADIf there are unpushed local commits, push them first:
git push origin master3. Determine the tag name
Compose a tag:
- Date portion: today's date as
YYYYMMDD - Slug: 2–4 word kebab-case summary of the dominant change (e.g.
core-bump,splitpane-fix,mixpanel-migration)
Ask the user to confirm or override the tag name before creating it.
4. Write the release notes
Pull commit subjects since the last release tag:
git log --oneline $(git tag --sort=-version:refname | head -1)..origin/masterGroup into sections: Features, Bug fixes, Tests, Chores. Omit sections that have no commits.
Create the Release
gh release create <tag> \
--title "Release - <human summary>" \
--notes "<release notes>"Publishing the release immediately triggers Deploy to Prod.
Monitor CI
gh run list --workflow=deploy-prod.yml --limit 3
gh run watch <run-id>Report the final run status. A successful run deploys the app and uploads chrome-extension.zip as a release asset.
Step 5: Wait for deploy + CI smoke (mandatory)
After publish, monitor both jobs in deploy-prod.yml:
gh run list --workflow=deploy-prod.yml --limit 3
gh run watch <run-id>The Post-deploy smoke (prod) job runs @smoke against https://app.zenuml.com (chromium). Do not skip waiting for it.
Step 5.5: Spot check (targeted coverage for this release)
Runs after Step 5 is green. Do not skip.
General workflow: spot-check skill.
Release-specific: understand what shipped between the previous published release and this tag, then verify those behaviors on production (or staging if prod is blocked) — not “run every recipe blindly.”
1. Establish the release delta
gh release list --repo ZenUml/web-sequence --exclude-drafts --limit 5 --json tagName
git fetch --tags
git log <prev-published-tag>..<new-tag> --onelineRead commits as product intent. For non-obvious subjects, git show <sha> before planning.
Mandatory triage table (every commit in the range):
| Category | Criteria | Plan action |
|---|---|---|
behavioral | User-visible app, diagram, editor, extension packaging, Firebase rules/functions affecting UX | ≥1 [ ] assertion |
instrumentation | Analytics only | Optional Mixpanel assertion or skip with reason |
infra/test/docs | CI, tests, docs, skills only | Skipped: … |
Spot check: N/A only if every commit is infra/test/docs. Output the triage table before the plan or N/A.
Show full SKILL.md (310 more words)Show less
2. Write the spot check plan (before browser)
Use the spot-check plan format. Target https://app.zenuml.com unless the release did not deploy.
Map delta themes to methods (examples):
| Themes in delta | Typical checks |
|---|---|
Diagram / @zenuml/core / vite.config.js | Edit DSL → SVG in #demo-frame; optional dsl-spot-check recipe on prod |
| Editor / modals / multi-page | Smoke paths from smoke.spec.js relevant to changed UI |
| Deploy / hosting only | @smoke on prod (likely already green in Step 5) + one manual DSL edit |
| Chrome extension | Note: extension ships as release asset; web app spot check does not replace Web Store verification |
3. Execute
Follow spot-check execution. @smoke passing in CI does not replace delta assertions you wrote.
Record pass / fail / skipped per planned [ ] line.
Report
Release Report: <tag>
- Commits released: <N>
- GitHub Release: <url>
- CI deploy: <url> — PASS|FAIL
- CI @smoke (prod): PASS|FAIL
- Spot check (delta): PASS|FAIL|N/A — <summary>
- Chrome extension asset: uploaded|skippedKnown CI Gotchas
These issues have been encountered and fixed — document here so they don't repeat:
| Symptom | Root cause | Fix applied |
|---|---|---|
ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION | pnpm 11 default: 24h age gate on new packages | pnpm-workspace.yaml: minimumReleaseAge: 0 |
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH (overrides) | package.json resolutions field → pnpm lockfile overrides mismatch across pnpm versions | workflow uses pnpm install --no-frozen-lockfile |
Cannot find module 'firebase-functions' | pnpm 10 strict module linking breaks firebase trigger parsing | functions/ uses npm install not pnpm install |
pnpm latest requires Node >= 22 | pnpm 11 dropped Node 20 | Node pinned to 22.x; pnpm pinned to v10 |
When creating the release tag, always tag HEAD of origin/master explicitly:
git tag v<tag> HEAD
git push origin v<tag>
gh release create v<tag> --title "..." --notes "..."Using gh release create without pre-pushing the tag can result in the release pointing at a stale commit.
Rules
- Never create a release tag pointing at a commit that is not on
origin/master. - Never force-push or delete release tags.
- Never release if required CI checks on the last merge commit are red — check with
gh run list --branch master --limit 5first. - If the deploy workflow fails, report the failure and the relevant log lines; do not retry automatically.
- After each retry, verify the tag points at the correct (latest) commit with
git ls-remote origin refs/tags/<tag>.
© 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
Just SKILL.md in .claude/skills/release-app of ZenUml/web-sequence.
Open the folder on GitHubat commit e38bd91
Compare with similar skills
Release App 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release App this skillZenUml/web-sequence | 150 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Visual Reviewai-dynamo/dynamo | 8.3k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Beautify GitHub Readmeoil-oil/beautify-github-readme | 1.8k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Archifymolvqingtai/WebChat | 2.6k | — | ~5.6k | Automated safety check: Pass | MIT | |
| Repomix Browser Extension Developeryamadashy/repomix | 29k | 1 repos | ~288 | Automated safety check: Pass | MIT | |
| GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram | 18k | — | ~427 | Automated safety check: Pass | MIT |
Similar skills
Beautify GitHub Readme
oil-oil/beautify-github-readme
Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets.
Archify
molvqingtai/WebChat
Create professional architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as standalone HTML files with SVG graphics, a built-in dark/light theme toggle, and one-click export to…
Repomix Browser Extension Developer
yamadashy/repomix
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content…
GitDiagram Repository Overview
ahmedkhaleel2004/gitdiagram
Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.
Voyager Contribute
voyager-crew/voyager
Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.
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.
Land PR
ZenUml/web-sequence
Merge a green ZenUML web-sequence PR into master and verify staging CI after merge.
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.
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.
Validate Branch
ZenUml/web-sequence
Run local validation checks for ZenUML web-sequence before pushing, opening a PR, or merging.
Ship Branch
ZenUml/web-sequence
Take the current ZenUML web-sequence branch from local validation through PR submission, green CI, and merge to master.
Related
Works with
Categories
Questions about Release App
What does Release App do?
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). Release App is an agent skill from ZenUml/web-sequence.5).
When should I use Release App?
Release App fits situations like: the user says release; ship to production; invokes /release-app.
How do I install Release App in Claude Code?
Run `npx skills add ZenUml/web-sequence --skill release-app -a claude-code`. Or copy the skill folder (.claude/skills/release-app in ZenUml/web-sequence) into .claude/skills/release-app in your project. Claude Code loads it when a task matches its description.
How do I install Release App in Codex?
Run `npx skills add ZenUml/web-sequence --skill release-app -a codex`. Or copy the skill folder (.claude/skills/release-app in ZenUml/web-sequence) into .agents/skills/release-app in your project. Codex loads it when a task matches its description.
Can I use Release App 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 release-app -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-app, .gemini/skills/release-app, .github/skills/release-app and .opencode/skills/release-app in your project.
What does Release App need to run?
Going by SKILL.md and its folder, Release App needs the command-line tools its instructions call (git, gh, pnpm and npm). Our summary lists: Node.js.
Does Release App access the network?
SKILL.md contains no URLs. Its commands use git, gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release App 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 Release App use?
Release App 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 Release App use?
About 1.7k tokens (SKILL.md is roughly 6.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 Release App?
Skills that share tags, products or a category with Release App: Visual Review (ai-dynamo/dynamo, 8.3k stars), Beautify GitHub Readme (oil-oil/beautify-github-readme, 1.8k stars), Archify (molvqingtai/WebChat, 2.6k stars) and Repomix Browser Extension Developer (yamadashy/repomix, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release App?
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.