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.
Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery.
Install Dev Verify
$ npx skills add hashgraph-online/awesome-codex-plugins --skill dev-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins dev-verify --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/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/Jason-chen-coder/dev-skills/skills/dev-verify .claude/skills/dev-verify && 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 "dev-verify" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Jason-chen-coder/dev-skills/skills/dev-verify into .claude/skills/dev-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-verify", 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/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Jason-chen-coder/dev-skills/skills/dev-verifyType 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 hashgraph-online/awesome-codex-plugins --skill dev-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins dev-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/Jason-chen-coder/dev-skills/skills/dev-verify .agents/skills/dev-verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dev-verify" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Jason-chen-coder/dev-skills/skills/dev-verify into .agents/skills/dev-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-verify", 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 hashgraph-online/awesome-codex-plugins --skill dev-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins dev-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/Jason-chen-coder/dev-skills/skills/dev-verify .cursor/skills/dev-verify && 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 "dev-verify" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Jason-chen-coder/dev-skills/skills/dev-verify into .cursor/skills/dev-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-verify", 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/hashgraph-online/awesome-codex-plugins.git --path plugins/Jason-chen-coder/dev-skills/skills/dev-verify--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 hashgraph-online/awesome-codex-plugins --skill dev-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins dev-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/Jason-chen-coder/dev-skills/skills/dev-verify .gemini/skills/dev-verify && 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 "dev-verify" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Jason-chen-coder/dev-skills/skills/dev-verify into .gemini/skills/dev-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-verify", 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 hashgraph-online/awesome-codex-plugins dev-verifyInstalls 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 hashgraph-online/awesome-codex-plugins --skill dev-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/Jason-chen-coder/dev-skills/skills/dev-verify .github/skills/dev-verify && 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 "dev-verify" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Jason-chen-coder/dev-skills/skills/dev-verify into .github/skills/dev-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-verify", 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 hashgraph-online/awesome-codex-plugins --skill dev-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins dev-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/Jason-chen-coder/dev-skills/skills/dev-verify .opencode/skills/dev-verify && 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 "dev-verify" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/Jason-chen-coder/dev-skills/skills/dev-verify into .opencode/skills/dev-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-verify", 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
dev-verify- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 538 words
- Files
- 3 (incl. references)
- Skills in repo
- 736
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery.
- Completion checks
- SKILL.md covers Load baseline, Choose evidence, Run and inspect and SDD alignment and completion, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Not general factual answers
What it does
Dev Verify is an agent skill from hashgraph-online/awesome-codex-plugins. Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery. Match checks to requested behavior and risk, inspect current evidence, and report limits. Use for completion checks, not general factual answers or a replacement for code review.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `examples.md` and `references/dev-baseline.md`).
It sits in Development. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.
When your agent uses it
- Completion checks
- Not general factual answers
- A replacement for code review
Example prompts
- “/dev-verify”
What it can do on your machine
Read from SKILL.md and the folder at commit 16b4156. 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
Dev Verify loads about 1.1k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 538 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 hashgraph-online/awesome-codex-plugins at commit 16b4156, republished under its Apache-2.0 licence (© hashgraph-online). 538 words, ~1,100 tokens.
Download SKILL.mdSave it as
.claude/skills/dev-verify/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- dev-verify
- description
- Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery. Match checks to requested behavior and risk, inspect current evidence, and report limits. Use for completion checks, not general factual answers or a replacement for code review.
Dev Verify
Make completion claims no broader than the evidence. This workflow verifies behavior and artifacts; it does not authorize commits, publishing, merge, or cleanup.
Load baseline
Read references/dev-baseline.md before execution. Resolve paths relative to this skill directory.
Choose evidence
Identify what the user expects to be true and the smallest sufficient proof. Use project commands and conventions; inspect their actual scope before relying on their names.
| Claim | Relevant proof |
|---|---|
| Behavior implemented | Tests or direct checks of observable acceptance criteria |
| Bug fixed | Original reproduction or faithful regression passes |
| Regression detects the defect | Observed failure on original behavior, or isolated mutation proof |
| Refactor preserves behavior | Relevant characterization tests pass before and after |
| Build/lint succeeds | Corresponding command completes successfully |
| UI works | Relevant rendered states and interactions, with viewport/device scope stated |
| Skill/document updated | Structure/link checks plus review of changed instructions/content |
Use focused checks for local changes. Broaden for shared contracts, state transitions, persistence, integrations, security, or project-required gates. Do not add tests that merely mirror reversible low-impact edits. A parser or keyword check validates structure, not instruction quality or system behavior.
Run and inspect
- Use fresh evidence from the final relevant file state. Evidence already produced and inspected during the task remains usable if the tested inputs, dependencies, and environment have not materially changed; do not rerun solely because a new message or handoff occurred.
- Record exact commands, exit status, and meaningful output. Inspect failures, skipped tests, and warnings that affect the claim. A command being started is not evidence of completion.
- Keep verification read-only with respect to source and the Git index. Run tools that generate artifacts in an isolated output location where needed. Do not fix code in an independent verification lane unless explicitly reassigned.
- A worker's summary is not enough: inspect its output and relevant artifacts, or independently reproduce the critical check. Scale repeated verification to remaining uncertainty.
- When a check fails, distinguish a regression from a pre-existing/environmental failure using evidence. Continue authorized corrective work in the appropriate lane, then rerun affected checks. Do not quietly waive a required failure.
Unavailable hardware, credentials, production access, or test tooling limits the claim. Complete all feasible checks and report missing proof without presenting a local substitute as equivalent.
Show full SKILL.md (172 more words)Show less
SDD alignment and completion
Use the current request and relevant existing SDD artifacts as acceptance criteria. If present, .claude/artifacts/{designs,plans,fixes}/ may contain the source contract; select by actual task/file relevance, not the number of artifacts. Later user corrections override stale artifacts.
For substantial work, map requirements to evidence and list missing coverage. Small changes need only a short verification statement. Report what changed, which checks passed or failed, and material residual limits; do not force a fixed checklist into every response.
Verification does not substitute for independent code review. A READY review is not proof that tests ran, and passing tests do not prove every review concern resolved. Use dev-code-review when available and required, or perform the equivalent independent review.
Multi-Agent Profile
Recommended agent_type: worker
When delegation is permitted, give the verifier the current task contract, change scope, and raw artifacts. The verifier evaluates evidence independently and reports claims checked, commands/results, and limitations without changing source or staging files. Follow docs/multi-agent-policy.md if this repository is available; these rules also apply to standalone installations.
© hashgraph-online, 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
Files
SKILL.md and 2 other files (references) in plugins/Jason-chen-coder/dev-skills/skills/dev-verify of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- examples.md
- references/dev-baseline.md
Open the folder on GitHubat commit 16b4156
Compare with similar skills
Dev Verify 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 |
|---|---|---|---|---|---|---|
| Dev Verify this skillhashgraph-online/awesome-codex-plugins | 1.2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| 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 hashgraph-online/awesome-codex-plugins
All 736 skills in this repoAnime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Related
Categories
Questions about Dev Verify
What does Dev Verify do?
Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery. Dev Verify is an agent skill from hashgraph-online/awesome-codex-plugins. Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery.
When should I use Dev Verify?
Dev Verify fits situations like: completion checks; not general factual answers; A replacement for code review.
How do I install Dev Verify in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill dev-verify -a claude-code`. Or copy the skill folder (plugins/Jason-chen-coder/dev-skills/skills/dev-verify in hashgraph-online/awesome-codex-plugins) into .claude/skills/dev-verify in your project. Claude Code loads it when a task matches its description.
How do I install Dev Verify in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill dev-verify -a codex`. Or copy the skill folder (plugins/Jason-chen-coder/dev-skills/skills/dev-verify in hashgraph-online/awesome-codex-plugins) into .agents/skills/dev-verify in your project. Codex loads it when a task matches its description.
Can I use Dev Verify 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 hashgraph-online/awesome-codex-plugins --skill dev-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-verify, .gemini/skills/dev-verify, .github/skills/dev-verify and .opencode/skills/dev-verify in your project.
What does Dev Verify need to run?
SKILL.md names no scripts, command-line tools or credentials: Dev Verify is instructions for the agent only.
Does Dev Verify 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 Dev Verify 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 Dev Verify use?
Dev Verify 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.
How many tokens does Dev Verify use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 893 tokens, read only when the agent opens those files.
What are the alternatives to Dev Verify?
Skills that share tags, products or a category with Dev Verify: 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 Dev Verify?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,232 GitHub stars. The repository holds 736 skills in this directory. The repository was last updated on October 6, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.