New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Dotnet PR Review

by rodri-oliveira-dev in rodri-oliveira-dev/Dapper-FluentMap

A skill your agent uses to review a Dapper-FluentMap pull request or diff for correctness, regressions, compatibility, tests, performance, security, packaging, release, and maintainability.

MITAuto-check passedDevelopment

Install Dotnet PR Review

skills CLI
$ npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill dotnet-pr-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rodri-oliveira-dev/Dapper-FluentMap dotnet-pr-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rodri-oliveira-dev/Dapper-FluentMap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dotnet-pr-review .claude/skills/dotnet-pr-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dotnet-pr-review
GitHub stars
454
Token cost
~807 tokens
SKILL.md length
383 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses to review a Dapper-FluentMap pull request or diff for correctness, regressions, compatibility, tests, performance, security, packaging, release, and maintainability.

  • Works in 8 steps: Read root AGENTS.md, the PR description,… → Understand the intended behavior before… → Review the diff first. Open full files… → …
  • Review a Dapper-FluentMap pull request
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Diff for correctness

What it does

Dotnet PR Review is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Use this skill to review a Dapper-FluentMap pull request or diff for correctness, regressions, compatibility, tests, performance, security, packaging, release, and maintainability. Do not use to implement PR changes unless explicitly asked.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with .NET. The repository describes itself as: Fluent mapping for Dapper, with conventions, immutable object materialization, analyzers, source generators, DI integration, and Dommel support. The licence is MIT.

When your agent uses it

  • Review a Dapper-FluentMap pull request
  • Diff for correctness
  • Maintainability
  • Implement PR changes unless explicitly asked

Example prompts

  • “/dotnet-pr-review”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Read root AGENTS.md, the PR description, linked issue, and the diff.
  2. Understand the intended behavior before evaluating the implementation.
  3. Review the diff first. Open full files only when the surrounding contract or call path is unclear.
  4. Check correctness, public API/source/binary/behavior compatibility, SemVer impact, Dapper behavior, global state/cache, concurrency…
  5. Confirm every finding is introduced or materially worsened by the diff.
  6. Describe a concrete failure scenario and a practical correction direction.
  7. Verify tests protect the changed behavior and that validation evidence matches the risk.
  8. Look for accidental scope expansion, unrelated modernization, PackageId/namespace/path confusion, or workflow assumptions that do not…

What it can do on your machine

Read from SKILL.md and the folder at commit 4f5a39f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dotnet PR Review loads about 807 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 383 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~807

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rodri-oliveira-dev/Dapper-FluentMap at commit 4f5a39f, republished under its MIT licence (© rodri-oliveira-dev). 383 words, ~807 tokens.

Download SKILL.mdSave it as .claude/skills/dotnet-pr-review/SKILL.md (or your agent's skills folder).
name
dotnet-pr-review
description
Use this skill to review a Dapper-FluentMap pull request or diff for correctness, regressions, compatibility, tests, performance, security, packaging, release, and maintainability. Do not use to implement PR changes unless explicitly asked.
license
MIT

Purpose

Review changes for real risk and observable behavior, producing actionable findings instead of cosmetic comments.

Review Process

  1. Read root AGENTS.md, the PR description, linked issue, and the diff.
  2. Understand the intended behavior before evaluating the implementation.
  3. Review the diff first. Open full files only when the surrounding contract or call path is unclear.
  4. Check correctness, public API/source/binary/behavior compatibility, SemVer impact, Dapper behavior, global state/cache, concurrency, dependencies, performance, security, tests, docs, CI, package output, and release safety.
  5. Confirm every finding is introduced or materially worsened by the diff.
  6. Describe a concrete failure scenario and a practical correction direction.
  7. Verify tests protect the changed behavior and that validation evidence matches the risk.
  8. Look for accidental scope expansion, unrelated modernization, PackageId/namespace/path confusion, or workflow assumptions that do not match this repository.

Severity

  • P0 - Blocker: data loss, critical security failure, unusable package, or unavoidable broad breakage.
  • P1 - High: likely functional bug, unintended breaking change, concurrency/global-state failure, meaningful vulnerability, or incorrect release/package behavior.
  • P2 - Medium: real defect in a limited scenario, missing tests for important behavior, or significant maintainability/performance risk.
  • P3 - Low: objective improvement that should not block merge by itself.

Do not assign high severity to style preferences already handled by .editorconfig, analyzers, or formatting tools.

Finding Format

Lead with findings. For each one include severity, file/line, problematic behavior, failure scenario, and correction direction. If no issues are found, say so clearly and mention any residual validation gaps.

Show full SKILL.md (140 more words)Show less

Dapper-FluentMap Review Focus

  • Does the diff preserve explicit mapping > convention > Dapper default precedence?
  • Does it keep normal Dapper queries distinct from FluentMap-controlled materialization paths?
  • Are global static configuration and SqlMapper.SetTypeMap effects isolated in tests?
  • Are nested/value-object claims proven end to end, not just by metadata?
  • Do package changes account for all five NuGet packages and independent identities?
  • Do release/workflow changes preserve main, version validation, artifact checks, provenance, and recovery behavior?

Restrictions

  • Do not rewrite the PR from preference.
  • Do not require a new abstraction without a concrete failure or maintenance risk.
  • Do not mark pre-existing unrelated behavior as a regression unless the diff materially increases risk.
  • Do not approve a risky PR merely because it builds.

Quality Bar

A good review prioritizes a small number of real, reproducible issues, explains impact clearly, and uses deterministic validation as evidence when possible.

© rodri-oliveira-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/dotnet-pr-review of rodri-oliveira-dev/Dapper-FluentMap.

Open the folder on GitHubat commit 4f5a39f

Compare with similar skills

Dotnet PR Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dotnet PR Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dotnet PR Review this skillrodri-oliveira-dev/Dapper-FluentMap454—~807Automated safety check: PassMIT
MAUI PR Performance Analysisdotnet/maui23k—~2.4kAutomated safety check: PassMIT
Code Reviewjonathanpeppers/dotnes780—~2.1kAutomated safety check: PassMIT
Gh Stackdotnet/macios2.9k3 repos~10kAutomated safety check: PassCustom licence
Open Pull RequestGremlinq/ExRam.Gremlinq187—~1.5kAutomated safety check: PassMIT
Pull RequestOpenCoreMMO/OpenCoreMMO481—~814Automated safety check: PassGPL-3.0

Similar skills

  • MAUI PR Performance Analysis

    dotnet/maui

    Official

    Interprets pinned managed benchmark evidence for a dotnet/maui pull request and writes a narrative for the performance review workflow, without running or publishing anything.

    23k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Review

    jonathanpeppers/dotnes

    Review dotnes pull requests against established repository rules.

    780 GitHub stars~2.1k tokensUpdated 17 days ago
    DevelopmentAuto-check passed

  • Gh Stack

    dotnet/macios

    Official

    Manage stacked branches and pull requests with the gh-stack GitHub CLI extension.

    2.9k GitHub starsUsed in 3 repos~10k tokens
    DevelopmentAuto-check passed

  • Open Pull Request

    Gremlinq/ExRam.Gremlinq

    A skill your agent uses when opening a pull request for the current branch, or when an existing pull request needs a better description - including when the check-description CI check has failed.

    187 GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Pull Request

    OpenCoreMMO/OpenCoreMMO

    Create a pull request for OpenCoreMMO following the project's PR template.

    481 GitHub stars~814 tokensUpdated 18 days ago
    DevelopmentAuto-check passed

  • Maintain DisCatSharp

    Aiko-IT-Systems/DisCatSharp

    Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.

    140 GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

More from rodri-oliveira-dev/Dapper-FluentMap

All 11 skills in this repo

  • Directory Build Organization

    rodri-oliveira-dev/Dapper-FluentMap

    Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props when present, and related repository build files.

    454 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed

  • Microbenchmarking

    rodri-oliveira-dev/Dapper-FluentMap

    Activate when BenchmarkDotNet is involved or when a .NET performance question requires controlled microbenchmark measurement.

    454 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Nuget Trusted Publishing

    rodri-oliveira-dev/Dapper-FluentMap

    Review, maintain, or set up NuGet trusted publishing (OIDC) for GitHub Actions.

    454 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Test Gap Analysis

    rodri-oliveira-dev/Dapper-FluentMap

    Pseudo-mutation analysis for behavioral blind spots: determine whether existing tests would catch meaningful caller-visible production changes, identify survivors or untested outcomes, and…

    454 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

  • Authoring GitHub Workflows

    rodri-oliveira-dev/Dapper-FluentMap

    Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.

    454 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Binlog Failure Analysis

    rodri-oliveira-dev/Dapper-FluentMap

    Analyze MSBuild binary logs to diagnose build failures. An agent skill from rodri-oliveira-dev/Dapper-FluentMap.

    454 GitHub stars~750 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Dotnet PR Review

What does Dotnet PR Review do?

A skill your agent uses to review a Dapper-FluentMap pull request or diff for correctness, regressions, compatibility, tests, performance, security, packaging, release, and maintainability. Dotnet PR Review is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Use this skill to review a Dapper-FluentMap pull request or diff for correctness, regressions, compatibility, tests, performance, security, packaging, release, and maintainability.

When should I use Dotnet PR Review?

Dotnet PR Review fits situations like: review a Dapper-FluentMap pull request; diff for correctness; maintainability; implement PR changes unless explicitly asked.

How do I install Dotnet PR Review in Claude Code?

Run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill dotnet-pr-review -a claude-code`. Or copy the skill folder (.agents/skills/dotnet-pr-review in rodri-oliveira-dev/Dapper-FluentMap) into .claude/skills/dotnet-pr-review in your project. Claude Code loads it when a task matches its description.

How do I install Dotnet PR Review in Codex?

Run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill dotnet-pr-review -a codex`. Or copy the skill folder (.agents/skills/dotnet-pr-review in rodri-oliveira-dev/Dapper-FluentMap) into .agents/skills/dotnet-pr-review in your project. Codex loads it when a task matches its description.

Can I use Dotnet PR Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill dotnet-pr-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dotnet-pr-review, .gemini/skills/dotnet-pr-review, .github/skills/dotnet-pr-review and .opencode/skills/dotnet-pr-review in your project.

What does Dotnet PR Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Dotnet PR Review is instructions for the agent only.

Does Dotnet PR Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dotnet PR Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dotnet PR Review use?

Dotnet PR Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dotnet PR Review use?

About 807 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dotnet PR Review?

Skills that share tags, products or a category with Dotnet PR Review: MAUI PR Performance Analysis (dotnet/maui, 23k stars), Code Review (jonathanpeppers/dotnes, 780 stars), Gh Stack (dotnet/macios, 2.9k stars) and Open Pull Request (Gremlinq/ExRam.Gremlinq, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dotnet PR Review?

rodri-oliveira-dev (a GitHub user) maintains it in rodri-oliveira-dev/Dapper-FluentMap, which has 454 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: rodri-oliveira-dev/Dapper-FluentMap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.