review-code

A code-review skill for Cratis projects. Cratis is a .NET framework that uses events and projections to build application data.

In plain words
What is it for?
It is for producing a structured review of C# architecture, commands, events, projections, routes, dependency discovery, and validation behavior.
Why use it?
It checks changed code against Cratis architecture and style rules, helping identify blocking mistakes and design violations before the code is accepted.

Skill for Claude CodeCodex

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/cratis/verticalslices/review-code
Any agent
npx skills add Cratis/VerticalSlices --skill review-code
Clone the repo
git clone --depth 1 https://github.com/Cratis/VerticalSlices

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,113 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00044 $0.01113
Opus 5 $0.00022 $0.00557
Sonnet 5 $0.00009 $0.00223
Haiku 4.5 $0.00004 $0.00111

Measured 2d ago against content hash 6cd509452e8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review-code 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 2d 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.

Origin

This is a copy

100% identical to review-code — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.ai/skills/review-code/SKILL.md · 87 lines

How it starts

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

Review changed code against all Cratis project standards and produce a structured report.

C# Architecture

  • Each slice is its own folder <Module>/<Feature>/<Slice>/<Slice>.cs with all backend artifacts — no top-level Features/ wrapper
  • Commands: record type with Handle() directly on them — no separate handler classes
  • Business rejection returns a ValidationResult / Result<TEvent, ValidationResult> (or validator) — never thrown from Provide()/Handle() (a throw is HTTP 500, not a validation error)
  • Fetched/computed handler data is in Provide(), not inline in Handle()
  • Events: record type, no mutable/nullable properties, past tense, never carry the event-source id
  • Identity concepts derive from EventSourceId<T> (not ConceptAs<Guid>)
  • Projections: AutoMap is on by default — .AutoMap() only after .NoAutoMap(); projections consume events, never read models
  • Model-bound query custom paths use [Path("...")], not [Route]
  • No service locator (IServiceProvider not injected); discover implementations with IInstancesOf<T>, not IEnumerable<T>
  • Namespace matches folder under the app source root (<RootNamespace>.<Module>.<Feature>.<Slice>)

C# Code Style

  • File-scoped namespaces; using directives alphabetically sorted
  • No unused using directives
  • is null / is not null — never == null / != null
  • var preferred over explicit types
  • No postfixes: Async, Impl, Service on class names
  • No regions
  • All public types, methods, and properties have multiline XML doc comments
  • <summary> tags always multiline — never /// <summary>Text</summary> on one line
  • Methods with parameters include <param name="..."> for each
  • Non-void methods include <returns>
  • Custom exception types only — never InvalidOperationException, ArgumentException, etc.
  • Exception XML docs start with "The exception that is thrown when …"
  • Copyright header on every file
  • Strongly-typed Concepts for all domain IDs/values (no raw Guid/string in domain models)

Read the full file on GitHub · 87 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 87 lines · 44 tokens per session scan A 6cd509452e8e

Subscribe to this mod's changes

review-code is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 1,113 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-code, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

ship-changes

Ship staged or unstaged local changes: create a branch, make logical commits, push to origin, open a PR with the correct description and label, merge it, prepare no-effect dispositions for related issues, and delete the branch locally and on origin. Use whenever the user asks to commit, push, create a PR, ship, or…

Cratis/AI · 74 tokens

cratis-command

Step-by-step guidance for creating a Cratis Arc command — [Command] record, Handle() method, CommandValidator, proxy generation, and React .use() hook with CommandDialog. Use when adding or creating a command, wiring up a form or button to the backend, working with IEventLog, CommandResult, CommandValidator…

Cratis/AI · 80 tokens

auth-and-identity

Use this skill for authentication, authorization, or identity in a Cratis Arc project — backend, frontend, or both. Covers identity providers (IProvideIdentityDetails), protecting commands/queries with authorization attributes, Microsoft Identity Platform, connecting backend identity to React, multi-tenant identity…

Cratis/AI · 88 tokens

cratis-react-page

Step-by-step guidance for building a React page in a Cratis Arc application — DataPage lists, CommandDialog toolbar actions, row selection, details components, observable queries, and MVVM. Use when building or modifying a page that lists/displays data, adding a table, wiring Add/Edit/Delete, or connecting a component…

Cratis/AI · 79 tokens

cratis-readmodel

Step-by-step guidance for creating a Cratis Chronicle read model from scratch — defining events, choosing between projection and reducer, [ReadModel] record with static query methods, and the generated TypeScript proxy in React. Use when creating a read model, working with [EventType], [ReadModel], IProjectionFor…

Cratis/AI · 100 tokens

cratis-specs-csharp

Step-by-step guidance for writing C# specs in Cratis with BDD Specification by Example — the Establish/Because/should pattern, for/when/and folder hierarchy, reusable given/ contexts, NSubstitute mocking, and the in-process scenario family. Use when writing C# unit or integration specs or structuring the for/when/and…

Cratis/AI · 101 tokens