Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Use after run-plan completes to independently verify the implementation.
Install Review Work
$ npx skills add tmdgusya/engineering-discipline --skill review-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tmdgusya/engineering-discipline review-work --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/tmdgusya/engineering-discipline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/review-work .claude/skills/review-work && 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-work" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/review-work into .claude/skills/review-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-work", 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/tmdgusya/engineering-discipline/tree/main/skills/review-workType 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 tmdgusya/engineering-discipline --skill review-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tmdgusya/engineering-discipline review-work --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/review-work .agents/skills/review-work && 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-work" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/review-work into .agents/skills/review-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-work", 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 tmdgusya/engineering-discipline --skill review-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tmdgusya/engineering-discipline review-work --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/review-work .cursor/skills/review-work && 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-work" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/review-work into .cursor/skills/review-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-work", 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/tmdgusya/engineering-discipline.git --path skills/review-work--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 tmdgusya/engineering-discipline --skill review-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tmdgusya/engineering-discipline review-work --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/review-work .gemini/skills/review-work && 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-work" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/review-work into .gemini/skills/review-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-work", 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 tmdgusya/engineering-discipline review-workInstalls 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 tmdgusya/engineering-discipline --skill review-work -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/review-work .github/skills/review-work && 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-work" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/review-work into .github/skills/review-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-work", 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 tmdgusya/engineering-discipline --skill review-work -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tmdgusya/engineering-discipline review-work --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/review-work .opencode/skills/review-work && 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-work" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/review-work into .opencode/skills/review-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-work", 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-work- GitHub stars
- 125
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,196 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- None found
At a glance
Use after run-plan completes to independently verify the implementation.
- Works in 5 steps: Load and Analyze Plan Document → Codebase Inspection → Test Execution → …
- The user says review the work
- SKILL.md covers Core Principle, Hard Gates, When To Use and When NOT To Use, plus 7 more sections
- Calls git
What it does
Review Work is an agent skill from tmdgusya/engineering-discipline. Use after run-plan completes to independently verify the implementation. Reads only the plan document and inspects the codebase from scratch — information-isolated from the execution context. Produces a structured review document with PASS/FAIL verdict. Triggers when the user says "review the work", "verify the implementation", "check if the plan was executed correctly".
Its SKILL.md is about 2.5k 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. The repository describes itself as: SKILL for engineering-discipline.
When your agent uses it
- The user says review the work
- Verify the implementation
- Check if the plan was executed correctly
Example prompts
- “review the work”
- “verify the implementation”
- “check if the plan was executed correctly”
- “/review-work”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Load and Analyze Plan Document
- Codebase Inspection
- Test Execution
- Git History Check (Informational)
- Verdict and Review Document
What it can do on your machine
Read from SKILL.md and the folder at commit 137dead. 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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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
Review Work loads about 2.5k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 1,196 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,196 words (~2,479 tokens).
“Independently verifies implementation results using only the plan document and the codebase. Receives no information from the execution process.”
- name
- review-work
Files
Just SKILL.md in skills/review-work of tmdgusya/engineering-discipline.
Open the folder on GitHubat commit 137dead
Compare with similar skills
Review Work 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 Work this skilltmdgusya/engineering-discipline | 125 | — | ~2.5k | Automated safety check: Pass | None | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 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 | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
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.
More from tmdgusya/engineering-discipline
All 11 skills in this repoClarification
tmdgusya/engineering-discipline
A skill your agent uses when a user's request is vague, ambiguous, or underspecified.
Clean AI Slop
tmdgusya/engineering-discipline
Corrective cleanup of AI-generated code — removes LLM-specific patterns while preserving behavior.
Karpathy
tmdgusya/engineering-discipline
Behavioral guardrails to prevent common LLM coding mistakes — enforces surgical changes, assumption verification, and scope discipline before and during implementation.
Plan Crafting
tmdgusya/engineering-discipline
A skill your agent uses when a task's scope is clear and multi-step implementation is needed, before touching code.
Run Plan
tmdgusya/engineering-discipline
A skill your agent uses when you have a written implementation plan to execute.
Systematic Debugging
tmdgusya/engineering-discipline
A skill your agent uses when encountering any bug, test failure, or unexpected behavior.
Related
Categories
Questions about Review Work
What does Review Work do?
Use after run-plan completes to independently verify the implementation. Review Work is an agent skill from tmdgusya/engineering-discipline. Use after run-plan completes to independently verify the implementation.
When should I use Review Work?
Review Work fits situations like: the user says review the work; verify the implementation; check if the plan was executed correctly.
How do I install Review Work in Claude Code?
Run `npx skills add tmdgusya/engineering-discipline --skill review-work -a claude-code`. Or copy the skill folder (skills/review-work in tmdgusya/engineering-discipline) into .claude/skills/review-work in your project. Claude Code loads it when a task matches its description.
How do I install Review Work in Codex?
Run `npx skills add tmdgusya/engineering-discipline --skill review-work -a codex`. Or copy the skill folder (skills/review-work in tmdgusya/engineering-discipline) into .agents/skills/review-work in your project. Codex loads it when a task matches its description.
Can I use Review Work 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 tmdgusya/engineering-discipline --skill review-work -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-work, .gemini/skills/review-work, .github/skills/review-work and .opencode/skills/review-work in your project.
What does Review Work need to run?
Going by SKILL.md and its folder, Review Work needs the command-line tools its instructions call (git).
Does Review Work access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Review Work 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 Work use?
No licence was found for Review Work or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Review Work use?
About 2.5k tokens (SKILL.md is roughly 9.9k 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 Work?
Skills that share tags, products or a category with Review Work: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Work?
tmdgusya (a GitHub user) maintains it in tmdgusya/engineering-discipline, which has 125 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on July 3, 2026.
Source: tmdgusya/engineering-discipline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.