Finishing a Development Branch
obra/superpowers
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.
Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions.
$ npx skills add inclusionAI/Choruz --skill choruz-record-demo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install inclusionAI/Choruz choruz-record-demo --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/inclusionAI/Choruz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/choruz-record-demo .claude/skills/choruz-record-demo && 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 "choruz-record-demo" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-record-demo into .claude/skills/choruz-record-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-record-demo", 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/inclusionAI/Choruz/tree/main/.agents/skills/choruz-record-demoType 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 inclusionAI/Choruz --skill choruz-record-demo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install inclusionAI/Choruz choruz-record-demo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/choruz-record-demo .agents/skills/choruz-record-demo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "choruz-record-demo" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-record-demo into .agents/skills/choruz-record-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-record-demo", 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 inclusionAI/Choruz --skill choruz-record-demo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install inclusionAI/Choruz choruz-record-demo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/choruz-record-demo .cursor/skills/choruz-record-demo && 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 "choruz-record-demo" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-record-demo into .cursor/skills/choruz-record-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-record-demo", 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/inclusionAI/Choruz.git --path .agents/skills/choruz-record-demo--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 inclusionAI/Choruz --skill choruz-record-demo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install inclusionAI/Choruz choruz-record-demo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/choruz-record-demo .gemini/skills/choruz-record-demo && 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 "choruz-record-demo" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-record-demo into .gemini/skills/choruz-record-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-record-demo", 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 inclusionAI/Choruz choruz-record-demoInstalls 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 inclusionAI/Choruz --skill choruz-record-demo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/choruz-record-demo .github/skills/choruz-record-demo && 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 "choruz-record-demo" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-record-demo into .github/skills/choruz-record-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-record-demo", 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 inclusionAI/Choruz --skill choruz-record-demo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install inclusionAI/Choruz choruz-record-demo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/choruz-record-demo .opencode/skills/choruz-record-demo && 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 "choruz-record-demo" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-record-demo into .opencode/skills/choruz-record-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-record-demo", 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.
choruz-record-demoRecord and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions.
Choruz Record Demo is an agent skill from inclusionAI/Choruz. Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions. Use for requested recordings, not as an automatic media requirement for every GUI pull request.
Its SKILL.md is about 1.1k 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 licence is Apache-2.0.
Read from SKILL.md and the folder at commit 7509c40. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Choruz Record Demo loads about 1.1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 570 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.
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.
The full file from inclusionAI/Choruz at commit 7509c40, republished under its Apache-2.0 licence (© inclusionAI). 570 words, ~1,085 tokens.
.claude/skills/choruz-record-demo/SKILL.md (or your agent's skills folder).Produce a local, watchable demonstration of verified product behaviour. The evidence-chain decision owns the provenance and publication boundaries.
Record the exact commit, checkout, serving origin, runtime mode and device revisions before capture. Use the repository's existing startup workflow after inspecting its configuration; do not improvise a second stack or overwrite a user's running workspace. A remote demonstration identifies both ends and the actual transport.
Use dedicated demonstration groups, workspaces and benign prompts. Prefer isolated browser state; when the user requests an existing authenticated browser, preserve it and record that exception. Never clear unrelated cookies, sessions or data to stage a demo.
Complete functional acceptance before recording a polished walkthrough. Real-product claims require real servers, transports and model rounds, not fixture agents, injected events or mocked responses. Keep failures visible in acceptance evidence even when the final showcase uses a subsequent successful run.
Choose a compact story at the user's requested duration. For a two-minute overview, give each feature enough time to show an action and its observable result; omit features that cannot be demonstrated honestly. Keep a fixed, readable viewport and capture only the intended application region.
Discover the available browser or native recording capability and read its instructions before using it. Use the supported CUA surface for user interaction. Prefer continuous capture for terminal output and animation. State-based screenshot encoding is suitable for a short edited walkthrough, but label it as such rather than claiming real-time video.
Each scenario's frames must come from one causal run. Do not splice an old successful response into a newer failed interaction. Separate scenarios may become explicitly separated chapters, with their provenance retained. Wait for concrete, uniquely identified UI results rather than using elapsed time or an echoed prompt as proof. To demonstrate an Agent tool action, show its identity, status and result; a spinner or final chat sentence alone is insufficient.
Keep credentials, pairing codes, private conversations, unrelated browser tabs and notifications outside the recording. Stage safe demo content instead of editing the product's rendered content. Stop capture before entering authentication material. Retakes, omitted waits, speed changes and chapter transitions are editorial changes, not evidence that the original operation was faster.
Store raw captures and output outside tracked source paths. Use the available media encoder for the requested format; MP4 is appropriate for a two-minute video, while GIF suits short loops. Preserve readable text and enough final-state hold time. Do not replace an existing artifact without resolving its exact path.
Inspect the encoded artifact itself: verify duration, dimensions, frame count and file size with media probing, then play it or decode representative frames from its beginning, every chapter transition and its ending. Check crop, ordering, text legibility and sensitive content. Source screenshots alone do not verify the encoded result.
Deliver the absolute local artifact path with a concise provenance summary: demonstrated commits, local/remote setup, actual model execution, and any cuts or state-based capture. A demo supports only the scenarios it shows; it does not replace automated tests or the separate acceptance report.
Recording does not authorize uploading media or editing a PR. Publish only when requested, verify the uploaded bytes and access path, and ensure the destination still refers to the demonstrated revision. Never commit recordings to main or a feature branch that will merge into main. Keep source-controlled skill instructions separate from generated media.
© inclusionAI, 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
Just SKILL.md in .agents/skills/choruz-record-demo of inclusionAI/Choruz.
Open the folder on GitHubat commit 7509c40
Choruz Record Demo 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 |
|---|---|---|---|---|---|---|
| Choruz Record Demo this skillinclusionAI/Choruz | 1k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 91k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
obra/superpowers
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.
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
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.
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…
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
inclusionAI/Choruz
A skill your agent uses when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in this repository; checks every new note for superseded active records, classifies implemented…
inclusionAI/Choruz
A skill your agent uses when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request…
inclusionAI/Choruz
Design, review, and diagnose Choruz tests and fixtures that can fail nondeterministically under CI concurrency: parallel Playwright workers sharing one PostgreSQL and one API, vitest workers, cargo…
inclusionAI/Choruz
A skill your agent uses when reviewing a pull request in this repository; orients the reviewer to Choruz's standards (AGENTS.md conventions, the PR test policy, Agent Notes, the CI gates) and the…
inclusionAI/Choruz
Create, restructure, review, audit, or migrate Choruz Markdown documentation (docs/, README, AGENTS.md, the in-app docs pages) using one owner per fact, tier placement, executed-operation…
inclusionAI/Choruz
A skill your agent uses when working in this repository to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or…
Categories
Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions. Choruz Record Demo is an agent skill from inclusionAI/Choruz. Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions.
Choruz Record Demo fits situations like: requested recordings; not as an automatic media requirement for every GUI pull request.
Run `npx skills add inclusionAI/Choruz --skill choruz-record-demo -a claude-code`. Or copy the skill folder (.agents/skills/choruz-record-demo in inclusionAI/Choruz) into .claude/skills/choruz-record-demo in your project. Claude Code loads it when a task matches its description.
Run `npx skills add inclusionAI/Choruz --skill choruz-record-demo -a codex`. Or copy the skill folder (.agents/skills/choruz-record-demo in inclusionAI/Choruz) into .agents/skills/choruz-record-demo in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add inclusionAI/Choruz --skill choruz-record-demo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/choruz-record-demo, .gemini/skills/choruz-record-demo, .github/skills/choruz-record-demo and .opencode/skills/choruz-record-demo in your project.
SKILL.md names no scripts, command-line tools or credentials: Choruz Record Demo is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Choruz Record Demo 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.
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Choruz Record Demo: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
inclusionAI (a GitHub organization) maintains it in inclusionAI/Choruz, which has 1,017 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: inclusionAI/Choruz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.