code-review
Offers a technical checklist and review heuristics specifically for C#/.NET and MAUI development.
Install
mkdir -p .claude/skills/code-review-jason-kerney && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15082" && unzip -o skill.zip -d .claude/skills/code-review-jason-kerney && rm skill.zipInstalls to .claude/skills/code-review-jason-kerney
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Technical code review guidance for WorkMood and similar .NET/MAUI projects. Covers correctness, testability, performance, idiomatic C#/.NET, and API design. Provides checklists, review heuristics, and verification steps for safe, incremental improvements.Key capabilities
- →Review code for correctness and safety
- →Assess testability of code changes
- →Evaluate performance aspects like allocations and UI responsiveness
- →Check for idiomatic .NET/C# patterns and project conventions
- →Review API and architecture clarity
- →Verify documentation currency
How it works
The skill guides technical code reviews for C#/.NET projects by providing a checklist covering correctness, testability, performance, idiomatic patterns, API design, and architecture. It also includes review heuristics and verification steps.
Inputs & outputs
When to use code-review
- →Reviewing a C# pull request
- →Checking MAUI UI responsiveness
- →Validating DI/SOLID implementation
About this skill
Code Review Skill for WorkMood
Purpose
This skill guides technical code review for C#/.NET (including MAUI) projects, with a focus on:
- Correctness and safety (does it work, is it robust?)
- Testability (can it be covered by unit/integration tests?)
- Performance (allocations, CPU, UI responsiveness)
- Idiomatic .NET/C# and project conventions (MVVM, DI, SOLID)
- API and architecture clarity
Review Checklist
- Correctness: Does the code do what it claims? Are edge cases handled?
- Tests: Are there tests? Do they cover happy/sad paths? Are they clear and minimal?
- Performance: Any obvious allocation, CPU, or UI responsiveness issues? (Use BenchmarkDotNet, PerfView, VS Diagnostics)
- Readability: Is the code clear, small, and idiomatic? Any long methods, magic values, or code smells?
- API Design: Are interfaces clear, minimal, and DI-friendly? Any leaky abstractions?
- MVVM/Architecture: Does it follow project patterns (MVVM, DI, shims, factories)?
- Documentation: Are comments, XML docs, and codexes up to date?
Review Heuristics
- Prefer small, focused diffs and single-responsibility changes.
- Write or update tests before/after changes to guarantee behavior.
- Use Arrange-Act-Assert in tests; prefer xUnit patterns.
- For performance: measure before/after, optimize only when needed.
- For refactoring: preserve behavior, commit in small increments, update codexes.
Example Review Prompts
- "/code-review [file.cs] Review for testability and performance."
- "/code-review [method] Is this idiomatic C#? Any code smells?"
- "/code-review [ViewModel] Does this follow MVVM and DI patterns?"
- "/code-review [diff] Are there any risks or missing tests?"
Verification Steps
- Build:
dotnet build --framework net9.0-windows10.0.19041.0 - Test:
dotnet test(or filter for specific tests) - Benchmark: Add BenchmarkDotNet, run microbenchmarks for hot paths
- Profile: Use PerfView or VS Diagnostic Tools for UI/CPU/memory issues
Resources
Maintenance
- Update this skill as project patterns or review priorities evolve.
- Ensure checklists and heuristics match current codexes and architecture docs.
When not to use it
- →When the project is not a .NET/MAUI project
- →When the focus is solely on style enforcement
- →When the task is not a technical code review
Limitations
- →The skill is tailored for WorkMood and similar .NET/MAUI projects.
- →Performance optimization is only recommended when needed, after measurement.
- →Refactoring should preserve behavior and be committed in small increments.
How it compares
This skill offers a structured and complete technical code review process with specific checklists and heuristics for .NET/MAUI projects, which is more detailed and focused than a general code review.
Compared to similar skills
code-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| code-review (this skill) | 0 | 5mo | No flags | Intermediate |
| code-coverage-with-gcov | 15 | 4mo | Review | Intermediate |
| dotnet-dev | 1 | 6mo | Review | Beginner |
| quality-checker | 0 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
code-coverage-with-gcov
gadievron
Add gcov code coverage instrumentation to C/C++ projects
dotnet-dev
GitTools
Expert guidance for .NET development in this repository. Use this skill for building, testing, debugging, and understanding project structure, coding conventions, dependency injection patterns, and testing practices.
quality-checker
rdkcentral
Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) on the MemCapture codebase. Use when validating code changes or debugging before committing.
migration-unit-testing
RobertoBorges
|
dotnet-code-analysis
managedcode
Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. Use when a .NET repo needs first-party code analysis, `EnableNETAnalyzers`, `AnalysisLevel`, or warning-as-error policy wired into build and CI.
dotnet-code-quality
albertoirurueta
Run this .NET/C# project or solution's Roslyn analyzers — StyleCop.Analyzers for style/formatting (the .NET equivalent of Checkstyle) and Microsoft.CodeAnalysis.NetAnalyzers' CA rules for code-quality/design/reliability/security bug detection (the .NET equivalent of PMD + SpotBugs combined) — via a