Subzeroclaw Contribute
genlayerlabs/subzeroclaw
Develop SubZeroClaw — the single-file ~550-line C agentic runtime.
Review a design doc against the actual codebase, find inconsistencies, and quiz the user on needed fixes.
Install Review Design
$ npx skills add janekbaraniewski/openusage --skill review-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install janekbaraniewski/openusage review-design --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/janekbaraniewski/openusage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/skills/review-design .claude/skills/review-design && 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-design" agent skill from https://github.com/janekbaraniewski/openusage/tree/main/docs/skills/review-design into .claude/skills/review-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-design", 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/janekbaraniewski/openusage/tree/main/docs/skills/review-designType 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 janekbaraniewski/openusage --skill review-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install janekbaraniewski/openusage review-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/janekbaraniewski/openusage.git skills-src && mkdir -p .agents/skills && cp -r skills-src/docs/skills/review-design .agents/skills/review-design && 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-design" agent skill from https://github.com/janekbaraniewski/openusage/tree/main/docs/skills/review-design into .agents/skills/review-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-design", 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 janekbaraniewski/openusage --skill review-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install janekbaraniewski/openusage review-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/janekbaraniewski/openusage.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/docs/skills/review-design .cursor/skills/review-design && 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-design" agent skill from https://github.com/janekbaraniewski/openusage/tree/main/docs/skills/review-design into .cursor/skills/review-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-design", 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/janekbaraniewski/openusage.git --path docs/skills/review-design--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 janekbaraniewski/openusage --skill review-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install janekbaraniewski/openusage review-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/janekbaraniewski/openusage.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/docs/skills/review-design .gemini/skills/review-design && 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-design" agent skill from https://github.com/janekbaraniewski/openusage/tree/main/docs/skills/review-design into .gemini/skills/review-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-design", 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 janekbaraniewski/openusage review-designInstalls 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 janekbaraniewski/openusage --skill review-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/janekbaraniewski/openusage.git skills-src && mkdir -p .github/skills && cp -r skills-src/docs/skills/review-design .github/skills/review-design && 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-design" agent skill from https://github.com/janekbaraniewski/openusage/tree/main/docs/skills/review-design into .github/skills/review-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-design", 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 janekbaraniewski/openusage --skill review-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install janekbaraniewski/openusage review-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/janekbaraniewski/openusage.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/docs/skills/review-design .opencode/skills/review-design && 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-design" agent skill from https://github.com/janekbaraniewski/openusage/tree/main/docs/skills/review-design into .opencode/skills/review-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-design", 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-design- GitHub stars
- 221
- Token cost
- ~892 tokens
- SKILL.md length
- 352 words
- Files
- 2 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review a design doc against the actual codebase, find inconsistencies, and quiz the user on needed fixes.
- Works in 4 steps: Load Design → Codebase Audit → Quiz Loop (CORE) → …
- Tasks that involve Architecture decision records
- SKILL.md covers Phase 0 — Load Design, Phase 1 — Codebase Audit, Phase 2 — Quiz Loop (CORE) and Phase 3 — Final Verification, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review Design is an agent skill from janekbaraniewski/openusage. Review a design doc against the actual codebase, find inconsistencies, and quiz the user on needed fixes. Loops until all issues are resolved. Use after /design-feature and before /implement-feature.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/review-checklist.md`).
It sits in Education, covering Architecture decision records. It works with OpenRouter. The repository describes itself as: The one dashboard you’ve been looking for — track spend and usage across Claude, Cursor, OpenRouter, Copilot, Gemini, Codex, and more. The licence is MIT.
When your agent uses it
- Tasks that involve Architecture decision records
Example prompts
- “/review-design”
Workflow steps
4 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 084bff5. 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 Design loads about 892 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 352 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 janekbaraniewski/openusage at commit 084bff5, republished under its MIT licence (© janekbaraniewski). 352 words, ~892 tokens.
Download SKILL.mdSave it as
.claude/skills/review-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- review-design
- description
- Review a design doc against the actual codebase, find inconsistencies, and quiz the user on needed fixes. Loops until all issues are resolved. Use after /design-feature and before /implement-feature.
- scope
- project
- keywords
- review, design, validate, quiz, codebase, verify
OpenUsage Design Doc Reviewer
Invocation: When a user wants to validate a design doc against the current codebase before implementing it.
Input: Design doc path or feature name (resolved to docs/<NAME>_DESIGN.md).
Phase 0 — Load Design
- Find the design doc. If path not given, search
docs/*_DESIGN.md. - Read the full design doc. Extract:
- Problem statement
- Affected subsystems
- Type definitions and interface changes
- Implementation tasks with file lists
- Confirm with the user which design doc to review.
Phase 1 — Codebase Audit
For each subsystem listed in the design doc's impact analysis:
- Read the primary files from
docs/skills/design-feature/references/subsystem-map.md. - Read every file referenced in the implementation tasks.
- Build a discrepancy list by checking each item in
references/review-checklist.md.
Focus on concrete mismatches. Don't flag style preferences or hypotheticals.
Phase 2 — Quiz Loop (CORE)
Present findings one at a time as questions. For each discrepancy:
## Issue N: <short title>
**Design says**: <quote or paraphrase from design doc>
**Codebase says**: <what actually exists, with file:line reference>
**Severity**: breaking | incorrect | stale | minor
**Question**: <specific question asking the user how to resolve this>
Options:
a) Update the design doc to match the codebase
b) Keep the design (codebase will change during implementation)
c) Something else — explainRules for the quiz loop:
- Present 1-3 issues per round (group related issues).
- Wait for the user's answer before proceeding.
- After the user answers, apply their decision:
- If (a): edit the design doc immediately.
- If (b): note it as "intentional change" — no edit needed.
- If (c): discuss, then apply the agreed resolution.
- After resolving a batch, re-scan affected areas for new issues introduced by the edits.
- Repeat until no discrepancies remain.
Show full SKILL.md (137 more words)Show less
Phase 3 — Final Verification
When no more issues are found:
- Re-read the design doc (it may have been edited during the quiz).
- Verify all implementation tasks still reference valid files and types.
- Confirm the task dependency order is still correct.
- Report:
## Review Complete
Design doc: <path>
Issues found: N
Issues resolved: N
Design doc edits: N
### Resolutions
- Issue 1: <title> — <resolution summary>
- Issue 2: <title> — <resolution summary>
### Ready for implementation
The design doc is consistent with the codebase. Run /implement-feature <name> to proceed.Rules
- Never skip Phase 1. Always audit the codebase — don't trust the design doc blindly.
- Never auto-fix without asking. Every discrepancy goes through the quiz.
- Always cite file:line. Vague references like "in the types file" are not acceptable.
- Stop if the design doc is fundamentally broken (e.g., references a subsystem that doesn't exist). Tell the user to re-run
/design-feature. - Don't review code style. Focus on structural correctness: types, interfaces, function signatures, file locations, config schema.
- Group related issues. If three fields on the same struct are wrong, that's one issue, not three.
© janekbaraniewski, 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 (references) in docs/skills/review-design of janekbaraniewski/openusage.
- SKILL.md
- references/review-checklist.md
Open the folder on GitHubat commit 084bff5
Compare with similar skills
Review Design 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 Design this skilljanekbaraniewski/openusage | 221 | — | ~892 | Automated safety check: Pass | MIT | |
| Subzeroclaw Contributegenlayerlabs/subzeroclaw | 137 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Yao Bayesian Skillyaojingang/yao-open-skills | 1.3k | — | ~956 | Automated safety check: Pass | MIT | |
| Doc Searchjellydn/my-ai-tools | 123 | — | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 91k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Yao Bayesian Skill
yaojingang/yao-open-skills
Convert uncertain real-world choices into an auditable Bayesian evidence-to-action report with priors, evidence grading, posterior update, action thresholds, sensitivity checks, multi-turn decision…
Doc Search
jellydn/my-ai-tools
Search project documentation — ADRs, wiki entries, conventions via ripgrep, qmd, fff, and ctx
PR Design Doc
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…
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
More from janekbaraniewski/openusage
Design Feature
janekbaraniewski/openusage
Design new features for OpenUsage with structured design docs and implementation tasks.
Implement Feature
janekbaraniewski/openusage
Implement a feature from an existing design doc. An agent skill from janekbaraniewski/openusage.
Openusage Provider
janekbaraniewski/openusage
Add new AI usage providers to the OpenUsage TUI dashboard. An agent skill from janekbaraniewski/openusage.
Related
Works with
Categories
Questions about Review Design
What does Review Design do?
Review a design doc against the actual codebase, find inconsistencies, and quiz the user on needed fixes. Review Design is an agent skill from janekbaraniewski/openusage. Review a design doc against the actual codebase, find inconsistencies, and quiz the user on needed fixes.
When should I use Review Design?
Review Design fits situations like: tasks that involve Architecture decision records.
How do I install Review Design in Claude Code?
Run `npx skills add janekbaraniewski/openusage --skill review-design -a claude-code`. Or copy the skill folder (docs/skills/review-design in janekbaraniewski/openusage) into .claude/skills/review-design in your project. Claude Code loads it when a task matches its description.
How do I install Review Design in Codex?
Run `npx skills add janekbaraniewski/openusage --skill review-design -a codex`. Or copy the skill folder (docs/skills/review-design in janekbaraniewski/openusage) into .agents/skills/review-design in your project. Codex loads it when a task matches its description.
Can I use Review Design 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 janekbaraniewski/openusage --skill review-design -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-design, .gemini/skills/review-design, .github/skills/review-design and .opencode/skills/review-design in your project.
What does Review Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Design is instructions for the agent only.
Does Review Design 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 Design 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 Design use?
Review Design 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 Design use?
About 892 tokens (SKILL.md is roughly 3.6k 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 581 tokens, read only when the agent opens those files.
What are the alternatives to Review Design?
Skills that share tags, products or a category with Review Design: Subzeroclaw Contribute (genlayerlabs/subzeroclaw, 137 stars), Yao Bayesian Skill (yaojingang/yao-open-skills, 1.3k stars), Doc Search (jellydn/my-ai-tools, 123 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.
Who maintains Review Design?
janekbaraniewski (a GitHub user) maintains it in janekbaraniewski/openusage, which has 221 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 10, 2026.
Source: janekbaraniewski/openusage on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.