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.
Review an Agent Skill for valid structure, clear triggers, usable instructions, current evidence, and risky or unclear actions.
Install Review Skill
$ npx skills add skilld-dev/skilld --skill review-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install skilld-dev/skilld review-skill --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/skilld-dev/skilld.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/review-skill .claude/skills/review-skill && 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 "review-skill" agent skill from https://github.com/skilld-dev/skilld/tree/main/skills/review-skill into .claude/skills/review-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-skill", 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/skilld-dev/skilld/tree/main/skills/review-skillType 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 skilld-dev/skilld --skill review-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install skilld-dev/skilld review-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/skilld.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/review-skill .agents/skills/review-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-skill" agent skill from https://github.com/skilld-dev/skilld/tree/main/skills/review-skill into .agents/skills/review-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-skill", 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 skilld-dev/skilld --skill review-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install skilld-dev/skilld review-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/skilld.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/review-skill .cursor/skills/review-skill && 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 "review-skill" agent skill from https://github.com/skilld-dev/skilld/tree/main/skills/review-skill into .cursor/skills/review-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-skill", 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/skilld-dev/skilld.git --path skills/review-skill--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 skilld-dev/skilld --skill review-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install skilld-dev/skilld review-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/skilld.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/review-skill .gemini/skills/review-skill && 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 "review-skill" agent skill from https://github.com/skilld-dev/skilld/tree/main/skills/review-skill into .gemini/skills/review-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-skill", 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 skilld-dev/skilld review-skillInstalls 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 skilld-dev/skilld --skill review-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/skilld-dev/skilld.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/review-skill .github/skills/review-skill && 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 "review-skill" agent skill from https://github.com/skilld-dev/skilld/tree/main/skills/review-skill into .github/skills/review-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-skill", 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 skilld-dev/skilld --skill review-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install skilld-dev/skilld review-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/skilld.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/review-skill .opencode/skills/review-skill && 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 "review-skill" agent skill from https://github.com/skilld-dev/skilld/tree/main/skills/review-skill into .opencode/skills/review-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-skill", 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
review-skill- GitHub stars
- 315
- Token cost
- ~648 tokens
- SKILL.md length
- 397 words
- Files
- 2 (incl. assets)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review an Agent Skill for valid structure, clear triggers, usable instructions, current evidence, and risky or unclear actions.
- Works in 12 steps: Confirm SKILL.md exists and its parent… → Confirm frontmatter uses supported… → Confirm the description says what the… → …
- Development work in your project
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review Skill is an agent skill from skilld-dev/skilld. Review an Agent Skill for valid structure, clear triggers, usable instructions, current evidence, and risky or unclear actions.
Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including assets (for example `assets/harness-request.md`).
It sits in Development. The repository describes itself as: Open-source, privacy friendly skills.sh alternative for humans and agents. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/review-skill”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Confirm SKILL.md exists and its parent directory matches its name.
- Confirm frontmatter uses supported fields and valid values.
- Confirm the description says what the Skill does and when to use it, in the third person, with the terms a user types.
- Follow every linked reference and script.
- Report missing or broken links.
- Reject symbolic links, special files, and paths that leave the Skill directory.
- Check instructions for missing inputs, unclear outcomes, and silent failure paths.
- Check commands for destructive scope, credential exposure, and unverified downloads.
- Check examples against the cited API or project source. If a runtime is available, run them and report each result that differs from the…
- Find repeated prose and material that belongs in a reference.
- Find text the reader already knows: domain or framework explanations, generic debug advice, changelog paraphrase, and internals the reader…
- For a package Skill, confirm the body names the package version it was tested against, once, in the first paragraph. Flag other version…
What it can do on your machine
Read from SKILL.md and the folder at commit 5797f37. 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
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.
Network
No URLs in SKILL.md.
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
Review Skill loads about 648 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 397 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 skilld-dev/skilld at commit 5797f37, republished under its MIT licence (© skilld-dev). 397 words, ~648 tokens.
Download SKILL.mdSave it as
.claude/skills/review-skill/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- review-skill
- description
- Review an Agent Skill for valid structure, clear triggers, usable instructions, current evidence, and risky or unclear actions.
Review a Skill
Review the supplied Skill as an Agent would use it.
Checks
- Confirm
SKILL.mdexists and its parent directory matches its name. - Confirm frontmatter uses supported fields and valid values.
- Confirm the description says what the Skill does and when to use it, in the third person, with the terms a user types.
- Follow every linked reference and script.
- Report missing or broken links.
- Reject symbolic links, special files, and paths that leave the Skill directory.
- Check instructions for missing inputs, unclear outcomes, and silent failure paths.
- Check commands for destructive scope, credential exposure, and unverified downloads.
- Check examples against the cited API or project source. If a runtime is available, run them and report each result that differs from the claim.
An example is each code block and each checkable prose claim: a default, a list, a count, error text, an exit code, or "X happens when Y".
Test the exact version the Skill names, never the repository head. Use the toolchain its users run, in each mode the claim covers, such as SSR, dev, and build.
Install it in an empty scratch directory with its own
pnpm-workspace.yaml. Prefer a local fixture to a live site. Never use personal credentials. For cloud-bound code, typecheck it and run it against in-memory stand-ins. Confirm a failing claim with a second probe before you report it. Mark each example executed, read from source, or unverified. - Find repeated prose and material that belongs in a reference.
- Find text the reader already knows: domain or framework explanations, generic debug advice, changelog paraphrase, and internals the reader cannot act on.
- For a package Skill, confirm the body names the package version it was tested against, once, in the first paragraph. Flag other version literals.
- Confirm the body covers each export, option, or symptom the description promises.
Show full SKILL.md (81 more words)Show less
Rank each finding:
error: following the Skill gives a wrong result, a failure, or a security gap.warning: an Agent would act wrongly on the claim, a failure stays silent, or a needed input is missing.note: precision, repetition, structure, or token cost.
Give the exact path, the line, and a direct fix. Do not rewrite the Skill unless the request asks for changes.
For a direct run, present the findings to the user. The user decides whether to apply them.
© skilld-dev, 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 (assets) in skills/review-skill of skilld-dev/skilld.
- SKILL.md
- assets/harness-request.md
Open the folder on GitHubat commit 5797f37
Compare with similar skills
Review Skill 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 |
|---|---|---|---|---|---|---|
| Review Skill this skillskilld-dev/skilld | 315 | — | ~648 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
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.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from skilld-dev/skilld
Generate Package Skill
skilld-dev/skilld
Generate or update an Agent Skill that teaches consumers one npm or local package the user maintains, including framework modules and wrappers.
Update Package Skill
skilld-dev/skilld
Updates an existing package Skill for a new release of its npm or local package by testing only what changed since the version the Skill names.
Skilld
skilld-dev/skilld
Operate skilld CLI for Skill discovery, use, installation, inspection, updates, authentication, configuration, restoration, and removal, including Repository, curator, and collection refs.
Generate Project Skill
skilld-dev/skilld
Generate or update an Agent Skill from the observed workflows, boundaries, and conventions of one software project.
Related
Categories
Questions about Review Skill
What does Review Skill do?
Review an Agent Skill for valid structure, clear triggers, usable instructions, current evidence, and risky or unclear actions. Review Skill is an agent skill from skilld-dev/skilld. Review an Agent Skill for valid structure, clear triggers, usable instructions, current evidence, and risky or unclear actions.
When should I use Review Skill?
Review Skill fits situations like: development work in your project.
How do I install Review Skill in Claude Code?
Run `npx skills add skilld-dev/skilld --skill review-skill -a claude-code`. Or copy the skill folder (skills/review-skill in skilld-dev/skilld) into .claude/skills/review-skill in your project. Claude Code loads it when a task matches its description.
How do I install Review Skill in Codex?
Run `npx skills add skilld-dev/skilld --skill review-skill -a codex`. Or copy the skill folder (skills/review-skill in skilld-dev/skilld) into .agents/skills/review-skill in your project. Codex loads it when a task matches its description.
Can I use Review Skill 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 skilld-dev/skilld --skill review-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-skill, .gemini/skills/review-skill, .github/skills/review-skill and .opencode/skills/review-skill in your project.
What does Review Skill need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Skill is instructions for the agent only.
Does Review Skill access the network?
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.
Is Review Skill 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 Review Skill use?
Review Skill 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 Review Skill use?
About 648 tokens (SKILL.md is roughly 2.6k 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 Review Skill?
Skills that share tags, products or a category with Review Skill: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Skill?
skilld-dev (a GitHub organization) maintains it in skilld-dev/skilld, which has 315 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.
Source: skilld-dev/skilld on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.