What is dotnet-techne-code-review?

A structured review guide for .NET pull requests, branches, code changes, and documents.

Use it for ordinary or adversarial reviews of .NET changes, including checks related to trimming, ahead-of-time compilation, and observability.

It helps check changes for correctness, performance, security, database and messaging issues, and production-readiness concerns.

dotnet-techne-code-review — Skill for Claude Code by Metalnib

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 Metalnib/dotnet-episteme-skills --skill dotnet-techne-code-review

Clone the repo

git clone --depth 1 https://github.com/Metalnib/dotnet-episteme-skills

Made for: Claude Code.

Or install dotnet-episteme-skills, the plugin that ships this one along with the rest of its 14 skills, 3 commands, 2 hooks, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/metalnib/dotnet-episteme-skills/dotnet-techne-code-review/github.svg)](https://agentmods.dev/skills/metalnib/dotnet-episteme-skills/dotnet-techne-code-review)

Your own site

<a href="https://agentmods.dev/skills/metalnib/dotnet-episteme-skills/dotnet-techne-code-review"><img src="https://agentmods.dev/badge/skills/metalnib/dotnet-episteme-skills/dotnet-techne-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/metalnib/dotnet-episteme-skills/dotnet-techne-code-review"><img src="https://agentmods.dev/badge/skills/metalnib/dotnet-episteme-skills/dotnet-techne-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,054 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00085	$0.01054
Opus 5	$0.00043	$0.00527
Sonnet 5	$0.00017	$0.00211
Haiku 4.5	$0.00009	$0.00105

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

Security

Grade A, and why

dotnet-techne-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 11d ago.

The scan reads SKILL.md. This mod also ships 14 executable files (scripts/affected-tests.ps1, scripts/affected-tests.sh, scripts/branch-diff.ps1, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/dotnet-techne-code-review/SKILL.md · 108 lines

How it starts

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

End-to-end .NET Code Review

Lean entrypoint for high-signal .NET review. Detailed commands/checklists/output requirements are split into reference files for progressive disclosure.

On Claude Code with this plugin installed, prefer /dotnet-episteme-skills:dotnet-review for parallel multi-agent review (4 domain specialists + a generalist + adversarial maintainer verification). This file remains the complete single-context procedure for all other tools.

Requirements

This skill requires:

Git for diff and commit analysis
Bash/Zsh (Linux/macOS) or PowerShell 5.1+ (Windows)
Agent tools with file read capability and shell command execution

Optional but recommended:

rg (ripgrep) for faster dependency searches on Linux/macOS
dotnet CLI for build verification

When to use this skill

Use this skill when the user asks for:

PR / branch / diff / commit-range review
"code review this implementation"
"critical review of ..."
"cynical review of ..."
adversarial / devil's-advocate review
production-readiness review (performance, AOT/trimming, security, observability, DB, messaging)

Reference files (read on demand)

references/scripts-and-context.md
- Read first when gathering change context and choosing script commands.
references/domain-checklists.md
- Read after context is loaded; focus on only the relevant sections for changed components.
references/output-contract.md
- Read before writing the final review output.
references/maintainer-playbook.md
- Read during the falsification pass (Step 3) to pressure-test findings before output.

Review modes

Standard mode (default)

Balanced review focused on correctness, maintainability, and risk.

Cynical mode (adversarial)

Use when request language is explicitly skeptical: "critical review", "cynical review", "tear this apart", "assume this is broken", "devil's advocate".

Mandates:

Assume defects exist until disproven.
Prefer failure-mode discovery over style nits.
Generate at least 5 issue hypotheses before finalizing.
Validate each hypothesis with evidence; remove weak/speculative findings.

Read the full file on GitHub · 108 lines

Files

What ships with it

18 files 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.

11d ago First seen · 108 lines · 85 tokens per session scan A e060421acab7

Subscribe to this mod's changes

dotnet-techne-code-review is a skill published in the GitHub repository Metalnib/dotnet-episteme-skills (12 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 1,054 once invoked, about $0.0004 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.

C# and .NET Code review Languages ai-agents ai-skills claude-code-skill code-analysis-true dotnet

resharper-clt

Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: jb inspectcode; jb cleanupcode; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally…

managedcode/dotnet-skills · 107 tokens

roslynator

Use the open-source free Roslynator analyzer packages and optional CLI for .NET. USE FOR: Roslynator.Analyzers setup; Roslynator CLI checks or cleanup; C# linting, static analysis, and code-fix automation. DO NOT USE FOR: overlapping analyzer packs with no consolidation plan; formatting-only work owned by another…

managedcode/dotnet-skills · 107 tokens

stylecop-analyzers

Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement…

managedcode/dotnet-skills · 142 tokens

dotnet-best-practices

Ensure .NET/C# code follows maintainable, modern best practices. Use when reviewing or improving C# code, solution structure, async patterns, dependency injection, or testability.

PracticalSwan/agent-skills · 43 tokens

cratis-engineering-csharp-conventions

Apply the Cratis C# house conventions when writing or reviewing C# in a Cratis repository - formatting, naming, records and primary constructors, nullable handling, XML documentation, custom exceptions, structured logging, dependency injection, and service lifetimes. Use for any "how should this be written" C# style…

Cratis/AI · 86 tokens

quickdup

Use the open-source free QuickDup clone detector for .NET repositories. Use when a repo needs duplicate C# code discovery, structural clone detection, DRY refactoring candidates, or repeatable duplication. USE FOR: the repo wants QuickDup; the team needs repeatable duplicate-code scans for C#; the user asks about DRY…

managedcode/dotnet-skills · 138 tokens