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.
AI DevKit · Final code review phase guidance for holistic pre-push review.
Install Dev Review
$ npx skills add codeaholicguy/ai-devkit --skill dev-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-review --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/codeaholicguy/ai-devkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dev-review .claude/skills/dev-review && 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-review" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-review into .claude/skills/dev-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-review", 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/codeaholicguy/ai-devkit/tree/main/skills/dev-reviewType 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 codeaholicguy/ai-devkit --skill dev-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dev-review .agents/skills/dev-review && 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-review" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-review into .agents/skills/dev-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-review", 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 codeaholicguy/ai-devkit --skill dev-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dev-review .cursor/skills/dev-review && 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-review" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-review into .cursor/skills/dev-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-review", 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/codeaholicguy/ai-devkit.git --path skills/dev-review--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 codeaholicguy/ai-devkit --skill dev-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dev-review .gemini/skills/dev-review && 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-review" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-review into .gemini/skills/dev-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-review", 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 codeaholicguy/ai-devkit dev-reviewInstalls 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 codeaholicguy/ai-devkit --skill dev-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dev-review .github/skills/dev-review && 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-review" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-review into .github/skills/dev-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-review", 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 codeaholicguy/ai-devkit --skill dev-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dev-review .opencode/skills/dev-review && 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-review" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-review into .opencode/skills/dev-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-review", 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-review- GitHub stars
- 1.6k
- Token cost
- ~851 tokens
- SKILL.md length
- 440 words
- Files
- 2
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
AI DevKit · Final code review phase guidance for holistic pre-push review.
- Works in 6 steps: Run npx ai-devkit@latest lint before… → If working on a named feature, run npx… → Check git status -sb and git diff --stat. → …
- The user wants code review
- SKILL.md covers Phase Contract and Code Review
- Calls npx and git
What it does
Dev Review is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Final code review phase guidance for holistic pre-push review. Use when the user wants code review, final lifecycle review, design alignment checks, integration risk review, or dev-lifecycle phase 9.
Its SKILL.md is about 850 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 Development, covering Code review. The repository describes itself as: The control plane for AI coding agents. The licence is Apache-2.0.
When your agent uses it
- The user wants code review
- Final lifecycle review
- Design alignment checks
- Integration risk review
Example prompts
- “/dev-review”
Requirements
- Node.js
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Run npx ai-devkit@latest lint before phase work.
- If working on a named feature, run npx ai-devkit@latest lint --feature .
- Check git status -sb and git diff --stat.
- Read feature docs and relevant changed files before findings.
- Apply the verify skill before claiming readiness.
- If parent dev-lifecycle established usable task tracing, emit review phase, progress, blocker/finding, next-step, and final…
What it can do on your machine
Read from SKILL.md and the folder at commit 7ef0cd5. 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:
npxgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and git, 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
Dev Review loads about 851 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 440 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 codeaholicguy/ai-devkit at commit 7ef0cd5, republished under its Apache-2.0 licence (© codeaholicguy). 440 words, ~851 tokens.
Download SKILL.mdSave it as
.claude/skills/dev-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- dev-review
- description
- AI DevKit · Final code review phase guidance for holistic pre-push review. Use when the user wants code review, final lifecycle review, design alignment checks, integration risk review, or dev-lifecycle phase 9.
Dev Review
Run final pre-push review for configured AI docs features. Before changing docs or code, propose the concrete review plan and wait for user approval unless the user already approved the exact phase plan.
Phase Contract
- Run
npx ai-devkit@latest lintbefore phase work. - If working on a named feature, run
npx ai-devkit@latest lint --feature <name>. - Check
git status -sbandgit diff --stat. - Read feature docs and relevant changed files before findings.
- Apply the
verifyskill before claiming readiness. - If parent
dev-lifecycleestablished usable task tracing, emit review phase, progress, blocker/finding, next-step, and final evidence/readiness events pertask.
Code Review
Use for Phase 9. Take a holistic review stance: findings first, ordered by severity, grounded in file/line references.
- Gather context: feature description, modified files, design docs, risky areas, tests already run.
- Verify design alignment by summarizing architectural intent and checking implementation matches.
- For each modified file, grep exported names to trace callers and dependents. Read relevant signatures, call sites, and type definitions.
- Check consistency against 1-2 similar modules.
- Search for existing utilities the new code could reuse or now duplicates. Flag near-matches honestly; do not force a wrong abstraction.
- Verify contract integrity at API, type, config, and schema boundaries.
- Check boundary discipline: external data is validated at edges, internal code is not littered with redundant guards, and transport/storage/framework types do not leak through domain APIs.
- Check reader load: needless layers, pass-through methods, broad shallow interfaces, mutable state scope, and unclear value ownership.
- Check domain fit: branch growth, synchronized flags, repeated shape assumptions, temporal decomposition, and missing state models.
- Check dependency health, including circular dependencies or version conflicts from new imports.
- Check breaking changes. For public/external APIs, recommend parallel change and deprecation over in-place mutation. For in-repo-only callers, all callers should be migrated and legacy APIs deleted.
- Check rollback safety, especially irreversible migrations or one-way data/state changes.
- Review file by file for correctness, logic, edge cases, redundancy, security, performance, error handling, and test coverage.
- Check cross-cutting concerns: naming conventions, documentation updates, missing tests, config/migration changes.
- Summarize blocking issues, important follow-ups, and nice-to-haves. Per finding include file, issue, impact severity, and recommendation.
- If task tracing is available, add blockers and set
blockedfor blocking findings; if review passes with final evidence, close the task pertask. - Complete final checklist: design match, no logic gaps, security addressed, integration points verified, tests cover changes, docs updated.
Show full SKILL.md (24 more words)Show less
Done: if the checklist passes, the feature is ready to push and create a PR. If blocking issues remain, return to dev-implementation or dev-testing.
© codeaholicguy, 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 1 other file in skills/dev-review of codeaholicguy/ai-devkit.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 7ef0cd5
Compare with similar skills
Dev Review 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 Review this skillcodeaholicguy/ai-devkit | 1.6k | — | ~851 | Automated safety check: Pass | Apache-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 | |
| Backend Code Reviewlangflow-ai/langflow | 156k | — | ~3.5k | Automated safety check: Notes | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Mole Bug Patternstw93/Mole | 70k | — | ~2k | Automated safety check: Pass | GPL-3.0 |
Similar skills
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.
Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
More from codeaholicguy/ai-devkit
All 28 skills in this repoAgent Management
codeaholicguy/ai-devkit
AI DevKit · Manage running AI agents with ai-devkit agent commands.
Dev Lifecycle
codeaholicguy/ai-devkit
AI DevKit · Orchestrator for structured SDLC phase skills. An agent skill from codeaholicguy/ai-devkit.
Task
codeaholicguy/ai-devkit
AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI.
Simplify Implementation
codeaholicguy/ai-devkit
AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability.
Agent Communication
codeaholicguy/ai-devkit
AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send.
Technical Writer
codeaholicguy/ai-devkit
AI DevKit · Review and improve documentation for novice users.
Related
Categories
Questions about Dev Review
What does Dev Review do?
AI DevKit · Final code review phase guidance for holistic pre-push review. Dev Review is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Final code review phase guidance for holistic pre-push review.
When should I use Dev Review?
Dev Review fits situations like: the user wants code review; final lifecycle review; design alignment checks; integration risk review.
How do I install Dev Review in Claude Code?
Run `npx skills add codeaholicguy/ai-devkit --skill dev-review -a claude-code`. Or copy the skill folder (skills/dev-review in codeaholicguy/ai-devkit) into .claude/skills/dev-review in your project. Claude Code loads it when a task matches its description.
How do I install Dev Review in Codex?
Run `npx skills add codeaholicguy/ai-devkit --skill dev-review -a codex`. Or copy the skill folder (skills/dev-review in codeaholicguy/ai-devkit) into .agents/skills/dev-review in your project. Codex loads it when a task matches its description.
Can I use Dev Review 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 codeaholicguy/ai-devkit --skill dev-review -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-review, .gemini/skills/dev-review, .github/skills/dev-review and .opencode/skills/dev-review in your project.
What does Dev Review need to run?
Going by SKILL.md and its folder, Dev Review needs the command-line tools its instructions call (npx and git). Our summary lists: Node.js.
Does Dev Review access the network?
SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Dev Review 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 Review use?
Dev Review 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 Review use?
About 851 tokens (SKILL.md is roughly 3.4k 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 Dev Review?
Skills that share tags, products or a category with Dev Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 156k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dev Review?
codeaholicguy (a GitHub user) maintains it in codeaholicguy/ai-devkit, which has 1,642 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 7, 2026.
Source: codeaholicguy/ai-devkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.