Project Development
guanyang/open-agent-hub
This skill should be used for project-level decisions about LLM-powered systems: whether an LLM is the right primitive for the task at hand, the shape of a multi-stage batch or agent pipeline, token…
Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia.
Install Review
$ npx skills add samchon/nestia --skill review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install samchon/nestia 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/samchon/nestia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review .claude/skills/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 "review" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/review into .claude/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/samchon/nestia/tree/master/.agents/skills/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 samchon/nestia --skill review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install samchon/nestia review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/review .agents/skills/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 "review" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/review into .agents/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 samchon/nestia --skill review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install samchon/nestia review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/review .cursor/skills/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 "review" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/review into .cursor/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/samchon/nestia.git --path .agents/skills/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 samchon/nestia --skill review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install samchon/nestia review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/review .gemini/skills/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 "review" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/review into .gemini/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 samchon/nestia 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 samchon/nestia --skill review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/review .github/skills/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 "review" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/review into .github/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 samchon/nestia --skill 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 samchon/nestia review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/review .opencode/skills/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 "review" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/review into .opencode/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
review- GitHub stars
- 2.2k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,104 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia.
- Works in 6 steps: Establish the complete change surface,… → Perform one complete round under the… → Reproduce every suspected defect before… → …
- Every self-review
- SKILL.md covers Non-Negotiable Review Law, Self-Review, Commit Early-Warning Pass and Solo Issue Discovery Rounds, plus 1 more section
- Calls git
What it does
Review is an agent skill from samchon/nestia. Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia. Use for every self-review or unqualified review request and as the default review mode inside issue campaigns. This skill never spawns review agents; use the multi-agent skill only when the user explicitly requests a team, parallel, or multi-agent review.
Its SKILL.md is about 2.1k 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 Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: NestJS Helper + AI Chatbot Development. The licence is MIT.
When your agent uses it
- Every self-review
- Unqualified review request and as the default review mode inside issue campaigns
- Explicitly requests a team
- Multi-agent review
Example prompts
- “Use the review skill to define exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia”
- “/review”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Establish the complete change surface, including the pull-request base-to-head diff and any uncommitted changes.
- Perform one complete round under the Non-Negotiable Review Law. Include correctness and boundaries, Express and Fastify behavior, Windows…
- Reproduce every suspected defect before accepting it.
- Apply every sound improvement and run the narrowest verification authorized by the owning workflow.
- If anything changed, restart at step 1 as a fresh full round.
- Finish only when a complete round finds nothing to improve. Report the final clean round and every verification that could not run.
What it can do on your machine
Read from SKILL.md and the folder at commit d3627e8. 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 loads about 2.1k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 1,104 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 samchon/nestia at commit d3627e8, republished under its MIT licence (© samchon). 1,104 words, ~2,081 tokens.
Download SKILL.mdSave it as
.claude/skills/review/SKILL.md (or your agent's skills folder).- name
- review
- description
- Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia. Use for every self-review or unqualified review request and as the default review mode inside issue campaigns. This skill never spawns review agents; use the multi-agent skill only when the user explicitly requests a team, parallel, or multi-agent review.
Review
Non-Negotiable Review Law
One reviewer performs every review in this skill from scratch over the entire declared surface. Do not spawn a subagent, delegate a concern, or load the discussion skill. Do not create a clone or worktree for solo review or Self-Review.
Choose the principled conclusion. Review duration, difficulty, and consequence surface are reasons to inspect more deeply and verify more carefully, never reasons to overlook a sound improvement, accept an unsupported claim, or lower the completion standard.
A complete round must satisfy all six rules:
- Whole surface: read every changed file and hunk. For issue discovery, audit the entire campaign scope. Never partition by file, package, concern, platform, or pass, and never substitute another reviewer's coverage.
- Consequence surface: inspect affected code paths, tests, generated artifacts, CI, packaging, documentation, and consumers. Trace side effects, state transitions, concurrency, platforms, boundaries, compatibility, and failure and recovery paths beyond the named symptom or diff.
- Fresh start: use the current state and repeat the whole inspection. Earlier rounds, sampled files, and a recheck of only the latest fix do not count as coverage.
- Unlimited rounds: whenever the reviewer applies an improvement or accepts a meaningful issue candidate, update the work and start another complete round. Stop only after a complete round produces nothing that survives verification.
- One immutable state: a round runs against one recorded state, dependency lock, provisioned workspace contract, supported environment contract, and mandatory test matrix. Issue discovery and committed pull-request review use an exact commit. A solo review records its exact starting diff and refreshes that snapshot after every edit; a review round must not race a source change. The multi-agent review procedure states how a team shares one snapshot.
- Auditable completeness: the reviewer accounts for every tracked file and every mandatory decorator, generator-output, consumer, boundary, transform-option, HTTP-adapter, packaging, and supported-platform matrix cell in the declared surface. Finding a candidate never ends or narrows the review. A skipped file, unprovisioned harness, unsupported claim, or unexecuted required cell makes the report
INCOMPLETE, neverCOMPLETE.
Self-Review
Self-Review and an unqualified review request use this solo workflow:
- Establish the complete change surface, including the pull-request base-to-head diff and any uncommitted changes.
- Perform one complete round under the Non-Negotiable Review Law. Include correctness and boundaries, Express and Fastify behavior, Windows and POSIX behavior, concurrency and state, data loss and security, cache and recovery invariants, public API and compatibility, generated SDK, Swagger, and e2e output, test isolation, CI and packaging, documentation, and migration effects.
- Reproduce every suspected defect before accepting it.
- Apply every sound improvement and run the narrowest verification authorized by the owning workflow.
- If anything changed, restart at step 1 as a fresh full round.
- Finish only when a complete round finds nothing to improve. Report the final clean round and every verification that could not run.
Self-Review does not authorize creating, pushing, updating, or merging a pull request. If the user separately requests one of those actions, follow the pull-request skill.
Commit Early-Warning Pass
A commit early-warning pass is not a review under this skill. It is the read-only per-commit reader a solo campaign author runs on every pushed commit while still implementing, required and defined by the solo campaign development document.
It delegates nothing the Non-Negotiable Review Law governs. The law governs the author's own round, which still runs alone over the whole surface before merge under all six rules. One commit is not a declared surface, a reported candidate is not an accepted finding, and the passes do not add up to a round.
Never call the pass a Self-Review, and never report it as one. A reader who sees that name concludes the gate already ran, and the whole-surface round disappears without anyone deciding to drop it.
Show full SKILL.md (479 more words)Show less
Solo Issue Discovery Rounds
Use these rounds only through the solo issue-campaign skill.
- Freeze one exact commit and record the dependency lock, provisioning command, and supported environment contract, as the issue-campaign skill defines them.
- Inventory all tracked files, package and public API families, implementation owners, generated artifacts, test harnesses, workflows, documentation contracts, supported platforms, and open and closed issue or pull-request history before examining candidates. Reconcile that inventory with
git ls-filesand with the campaign's coverage matrix. A grep lens, a sampled file set, or a statement that the surface was reviewed is not coverage. - Audit the entire inventory yourself and execute the whole campaign matrix. Inspect source, tests, documentation, CI, packaging, generated artifacts, platform behavior, upstream and downstream provenance, and history against the development skill's Forbidden section. Continue through the full inventory after finding a candidate.
- Record every raw candidate, killed hypothesis, command, and artifact in the campaign knowledge base against the exact commit and environment. Do not silently discard a suspicion because it looks duplicative or inconvenient.
- Reopen each candidate from primary evidence in a fresh state, reproduce it, verify ownership and provenance, trace its complete consequence surface, and compare existing issues and pull requests. A defect that actually belongs to
typia,ttsc, or NestJS is reported upstream, not filed here. - Record accept, partial acceptance, rewrite, combine, split, reject, or defer with the supporting evidence, so a later round does not rediscover a rejected premise as new. Implementation mechanisms remain hypotheses.
- Start another complete full-scope round against the same state whenever the round produced a candidate, and keep repeating until one round adds nothing the earlier rounds of this phase had not already recorded. Only that round ends the discovery phase and releases its adjudicated candidates for publication when the campaign is authorized to publish. After the authorized implementation flow merges, freeze the new integrated commit and run the same loop again. A prior finding never permits narrowing the next round to its owner or neighbors.
- End discovery only when one complete fresh round over the entire scope finishes its census and matrix and produces no meaningful candidate after fact-checking. Any verified in-repository correctness, contract, data-integrity, build, test-oracle, documentation, packaging, workflow, or Forbidden violation is meaningful regardless of severity, rarity, legacy status, or malformed-input trigger. An unresolved or deferred verified defect blocks the campaign, and green existing suites cannot satisfy the stop rule.
Explicit Multi-Agent Reviews
When the user explicitly asks for a team, parallel, or multi-agent review, load the multi-agent skill and its review procedure instead of this workflow. It inherits the same whole-surface, immutable-state, and auditable-completeness law while defining independent parallel reviewers, agent briefing, and lead and critic adjudication. A Research Review Round that needs external primary sources or sibling-repository provenance, such as the upstream typia and ttsc checkouts or the authoritative OpenAPI specification, lives there too.
© samchon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/review of samchon/nestia.
Open the folder on GitHubat commit d3627e8
Compare with similar skills
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 |
|---|---|---|---|---|---|---|
| Review this skillsamchon/nestia | 2.2k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Project Developmentguanyang/open-agent-hub | 975 | 2 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Swarm Parallel Dispatchlangchain-ai/langchain-skills | 1.3k | — | ~3k | Automated safety check: Pass | MIT | |
| Fable Foremanolsenbrands/fable-foreman | 142 | — | ~5.2k | Automated safety check: Pass | MIT | |
| Agents Buildaws/agent-toolkit-for-aws | 2.8k | — | ~2.3k | Automated safety check: Notes | Apache-2.0 | |
| Omnigent Agent Builderomnigent-ai/omnigent | 11k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Swarm Parallel Dispatch
langchain-ai/langchain-skills
Fans a list of independent items out to subagents in parallel, merges the results back into a table and supports retrying only the rows that failed.
Fable Foreman
olsenbrands/fable-foreman
Turns the lead model into a foreman that plans, routes and verifies while cheaper Claude, Codex or Grok workers do the typing, using a per-machine routing card.
- Official
Agents Build
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
Omnigent Agent Builder
omnigent-ai/omnigent
Gives patterns for generating a minimal, valid Omnigent agent directory: the config.yaml fields, the right executor type, and the files each agent needs.
Feishu Multi Agent
hyperlist/feishu-multi-agent
飞书多 Agent 系统搭建指南。当用户要求创建新的功能 Agent、配置飞书群聊绑定、 搭建多 Agent 协作系统时激活此 skill。
More from samchon/nestia
All 10 skills in this repoProject
samchon/nestia
Defines the nestia product contract, workspace layout, package boundaries, the Go plugin composition model, and canonical commands.
Contracts
samchon/nestia
Defines self-acknowledgments for production declarations and tests.
Issue Campaign
samchon/nestia
Defines the default solo repository-wide issue campaign for nestia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo…
Pull Request
samchon/nestia
Defines nestia branch, commit, pull-request, check, and merge workflows.
Development
samchon/nestia
Defines nestia implementation rules, testing standards, validation, consequence analysis, and change integrity.
Discussion
samchon/nestia
Runs structured multi-agent discussions for open-ended nestia topics.
Related
Categories
Questions about Review
What does Review do?
Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia. Review is an agent skill from samchon/nestia. Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia.
When should I use Review?
Review fits situations like: every self-review; unqualified review request and as the default review mode inside issue campaigns; explicitly requests a team; multi-agent review.
How do I install Review in Claude Code?
Run `npx skills add samchon/nestia --skill review -a claude-code`. Or copy the skill folder (.agents/skills/review in samchon/nestia) into .claude/skills/review in your project. Claude Code loads it when a task matches its description.
How do I install Review in Codex?
Run `npx skills add samchon/nestia --skill review -a codex`. Or copy the skill folder (.agents/skills/review in samchon/nestia) into .agents/skills/review in your project. Codex loads it when a task matches its description.
Can I use 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 samchon/nestia --skill 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/review, .gemini/skills/review, .github/skills/review and .opencode/skills/review in your project.
What does Review need to run?
Going by SKILL.md and its folder, Review needs the command-line tools its instructions call (git).
Does Review 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 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 use?
Review 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 use?
About 2.1k tokens (SKILL.md is roughly 8.3k 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?
Skills that share tags, products or a category with Review: Project Development (guanyang/open-agent-hub, 975 stars), Swarm Parallel Dispatch (langchain-ai/langchain-skills, 1.3k stars), Fable Foreman (olsenbrands/fable-foreman, 142 stars) and Agents Build (aws/agent-toolkit-for-aws, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review?
samchon (a GitHub user) maintains it in samchon/nestia, which has 2,179 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: samchon/nestia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.