Code Review

Code Review is a skill for Claude Code, Codex from vinilana/dotcontext. It costs 12 tokens per session (1,427 once invoked), scanned A, original, MIT.

A code-review guide for changes in the dotcontext CLI project. It checks code quality, design patterns, project conventions, and best practices against that project’s TypeScript structure.

In plain words
What is it for?
Use it when reviewing a pull request, validating work, or checking new TypeScript services, generators, utilities, and MCP gateway handlers in the dotcontext project.
Why use it?
It helps reviewers spot code that conflicts with existing architecture or standards before it is merged. It also provides a consistent way to assess pull requests and changes to services, generators, utilities, and gateway handlers.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when reviewing a pull request, validating work, or checking new TypeScript services, generators, utilities, and MCP gateway handlers in the dotcontext project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vinilana/dotcontext/code-review
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add vinilana/dotcontext --skill code-review
Clone the repo
git clone --depth 1 https://github.com/vinilana/dotcontext

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Code Review

README.md
[![agentmods](https://agentmods.dev/badge/skills/vinilana/dotcontext/code-review/github.svg)](https://agentmods.dev/skills/vinilana/dotcontext/code-review)
Your own site
<a href="https://agentmods.dev/skills/vinilana/dotcontext/code-review"><img src="https://agentmods.dev/badge/skills/vinilana/dotcontext/code-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Code Review

Your own site · 80×15
<a href="https://agentmods.dev/skills/vinilana/dotcontext/code-review"><img src="https://agentmods.dev/badge/skills/vinilana/dotcontext/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,427 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01427
Opus 5.5 $0.00005 $0.00571
Sonnet 5.5 $0.00002 $0.00285
Haiku 4.5 $0.00001 $0.00143

Measured 1mo ago against content hash a5106488c90b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Code Review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.context/skills/code-review/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review

Guidelines for reviewing code changes in the @dotcontext/cli project.

When to Use

  • Reviewing a pull request or diff
  • Validating code during the Review (R) or Validation (V) phases of the PREVC workflow
  • Checking a new service, generator, or utility for adherence to project patterns
  • Evaluating MCP gateway handler implementations

Project Standards

TypeScript Configuration

  • Target: ES2020, Module: CommonJS
  • Strict mode enabled ("strict": true)
  • Declarations and source maps generated
  • Path alias: @generators/agents/* maps to src/generators/agents/*

Code Organization Patterns

Service Layer (22 services in src/services/):

  • Each service lives in its own directory under src/services/
  • Exports through index.ts barrel files
  • Constructor takes an options object or required config
  • Methods are async where I/O is involved
  • Example: FillService, WorkflowService, AIContextMCPServer

Generators (src/generators/):

  • Separate generators for docs, agents, plans, skills
  • Accept options objects, return typed result objects (e.g., SkillGeneratorResult)
  • Use frontmatter serialization from src/types/scaffoldFrontmatter.ts

Utilities (src/utils/):

  • Pure functions or thin wrappers: frontMatter.ts, contentSanitizer.ts, gitService.ts
  • CLI UI abstraction: cliUI.ts with CLIInterface type
  • i18n: i18n.ts with TranslateFn type and en/pt-BR locale support

MCP Gateway Handlers (src/services/mcp/gateway/):

  • One file per gateway: explore.ts, context.ts, sync.ts, etc.
  • Exports: handler function, params type, options type, action type
  • Uses createJsonResponse/createErrorResponse/createTextResponse from response.ts
  • Barrel re-export through index.ts and gatewayTools.ts

Review Checklist

Architecture
  • New code follows the service/generator/util separation
  • No direct file I/O in generators -- delegate to services or fs-extra
  • MCP handlers do not use console.log (use process.stderr.write for debug output)
  • repoPath is never hardcoded; always resolved through options or getRepoPath()

Read the full file on GitHub · 137 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 137 lines · 12 tokens per session scan A a5106488c90b

Subscribe to this mod's changes

Code Review is a skill published in the GitHub repository vinilana/dotcontext (573 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 1,427 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens