agentmods.dev

PR Review

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

A pull-request review guide for checking changes against a project's team standards, architecture, tests, and commit conventions.

In plain words
What is it for?
Use it to review the scope and history of a pull request, check affected project layers, verify commit messages, and confirm architectural and testing expectations.
Why use it?
It helps catch quality, design, testing, and process problems before a pull request is merged.

Skill for Claude CodeCodex

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

not rated 565 +4 1mo ago A scan 12 tokens original MIT
View the source file vinilana/dotcontext
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.

agentmods
npx agentmods add skills/vinilana/dotcontext/pr-review
Any agent
npx skills add vinilana/dotcontext --skill pr-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 PR Review

README.md
[![agentmods](https://agentmods.dev/badge/skills/vinilana/dotcontext/pr-review.svg)](https://agentmods.dev/skills/vinilana/dotcontext/pr-review)
Your own site
<a href="https://agentmods.dev/skills/vinilana/dotcontext/pr-review"><img src="https://agentmods.dev/badge/skills/vinilana/dotcontext/pr-review.svg" alt="Measured on agentmods" 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,245 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.01245
Opus 5 $0.00006 $0.00622
Sonnet 5 $0.00002 $0.00249
Haiku 4.5 $0.00001 $0.00125

Measured 6d ago against content hash 82f234190a90, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

PR 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 6d 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/pr-review/SKILL.md · 154 lines

How it starts

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

PR Review

Review pull requests for the @dotcontext/cli project against established patterns and quality standards.

When to Use

  • Reviewing a PR before merge
  • Validating changes during the Review (R) or Validation (V) phases
  • Checking that a PR meets the project's architectural and testing standards

PR Review Process

1. Understand the Change Scope

Check which areas are affected:

# View changed files grouped by area
git diff main...HEAD --stat

Map changes to project layers:

  • src/services/mcp/ -- MCP server and gateway tools
  • src/services/<domain>/ -- Service layer business logic
  • src/generators/ -- Scaffold generation
  • src/workflow/ -- PREVC workflow system
  • src/utils/ -- Shared utilities
  • src/index.ts -- CLI command definitions
  • .context/ -- Documentation and scaffolding content

2. Verify the Commit History

This project uses Conventional Commits:

<type>(<scope>): <description>

Check that:

  • Each commit has a valid type (feat, fix, refactor, docs, test, chore)
  • Scope matches the primary area of change (see commit-message skill for scope list)
  • Messages are in imperative mood ("add", not "added")
  • Breaking changes use ! suffix and BREAKING CHANGE: footer

3. Architecture Review

Service Layer Compliance
  • New services follow the directory-per-service pattern under src/services/
  • Services export through index.ts barrel files
  • Constructor accepts options object; async init is a separate method
  • Dependencies are injectable (like contextBuilder in AIContextMCPServer)
MCP Tool Changes
  • Zod schemas have .describe() on every parameter
  • Gateway handler covers all actions in the enum (no unreachable branches)
  • Responses use createJsonResponse/createErrorResponse from response.ts
  • New types exported through gatewayTools.ts barrel
  • Total MCP tool count remains manageable (currently 9)
  • Tool description strings include all action names for AI discovery

Read the full file on GitHub · 154 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. 6d ago First seen · 154 lines · 12 tokens per session scan A 82f234190a90

Subscribe to this mod's changes

PR Review is a skill published in the GitHub repository vinilana/dotcontext (565 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,245 once invoked, about $0.0001 per session on Opus 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.

Code reviewGit and workflow
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens