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 Library Change

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

A skill your agent uses when changing Dapper-FluentMap production code, public contracts, project files, PackageIds, package metadata, dependencies, or related tests.

MITAuto-check passedDevelopment

Install Dotnet Library Change

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

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

GitHub CLI
$ gh skill install rodri-oliveira-dev/Dapper-FluentMap dotnet-library-change --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-library-change .claude/skills/dotnet-library-change && 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-library-change
GitHub stars
453
Token cost
~1.1k tokens
SKILL.md length
463 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when changing Dapper-FluentMap production code, public contracts, project files, PackageIds, package metadata, dependencies, or related tests.

  • Works in 10 steps: Read root AGENTS.md and the files… → Identify the affected package(s):… → Determine whether the change affects… → …
  • Changing Dapper-FluentMap production code
  • Calls dotnet
  • Public contracts

What it does

Dotnet Library Change is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Use this skill when changing Dapper-FluentMap production code, public contracts, project files, PackageIds, package metadata, dependencies, or related tests. Do not use for pure CI/release work or behavior-preserving refactoring as the primary task.

Its SKILL.md is about 1.1k 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 Refactoring. 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

  • Changing Dapper-FluentMap production code
  • Public contracts
  • Package metadata
  • Pure CI/release work

Example prompts

  • “/dotnet-library-change”

Workflow steps

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

  1. Read root AGENTS.md and the files directly related to the requested change.
  2. Identify the affected package(s): Dapper.FluentMap, Dapper.FluentMap.Dommel, FluentMap.DependencyInjection, FluentMap.Analyzers, or…
  3. Determine whether the change affects public API, source/binary/behavior compatibility, target frameworks, dependency ranges, Dapper/Dommel…
  4. Preserve independent identities: project name, path, assembly name, namespace, and NuGet PackageId are not interchangeable.
  5. Implement the smallest coherent change using existing project patterns.
  6. Add or update tests for observable behavior changes; use regression tests for bug fixes.
  7. Update consumer documentation and changelog only when the public contract or documented behavior changes.
  8. For dependency, target, PackageId, metadata, or pack output changes, combine with ci-release-governance.
  9. Run targeted validation first, then broader solution or package validation when risk requires it.
  10. Review the full diff for unrelated modernization, formatting churn, project metadata drift, or weakened validation.

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

    Shell commands in SKILL.md call:

    • dotnet

    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 Library Change loads about 1.1k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 463 words of instructions outside code blocks.

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

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). 463 words, ~1,089 tokens.

Download SKILL.mdSave it as .claude/skills/dotnet-library-change/SKILL.md (or your agent's skills folder).
name
dotnet-library-change
description
Use this skill when changing Dapper-FluentMap production code, public contracts, project files, PackageIds, package metadata, dependencies, or related tests. Do not use for pure CI/release work or behavior-preserving refactoring as the primary task.
license
MIT

Purpose

Guide small, safe changes to this public multi-package .NET library while preserving build, tests, packaging, and public compatibility.

When To Use

  • Changes under src/**.
  • Behavior changes requiring tests under test/**.
  • Changes to .csproj, targets, dependencies, public types/members, XML docs, or package metadata.
  • Any task that may affect package identity, assembly identity, namespace, dependency ranges, trimming/AOT annotations, analyzers, generators, or consumer compatibility.

When Not To Use

  • Behavior-preserving refactoring is the main task: use dotnet-refactoring-engineer.
  • Workflows, release, NuGet publishing, or recovery are the main task: use ci-release-governance.
  • Reviewing an existing PR/diff is the task: use dotnet-pr-review.
  • The task changes only agent guidance or documentation with no library behavior impact.

Process

  1. Read root AGENTS.md and the files directly related to the requested change.
  2. Identify the affected package(s): Dapper.FluentMap, Dapper.FluentMap.Dommel, FluentMap.DependencyInjection, FluentMap.Analyzers, or FluentMap.Generators.
  3. Determine whether the change affects public API, source/binary/behavior compatibility, target frameworks, dependency ranges, Dapper/Dommel integration, global state/cache, package output, or documentation.
  4. Preserve independent identities: project name, path, assembly name, namespace, and NuGet PackageId are not interchangeable.
  5. Implement the smallest coherent change using existing project patterns.
  6. Add or update tests for observable behavior changes; use regression tests for bug fixes.
  7. Update consumer documentation and changelog only when the public contract or documented behavior changes.
  8. For dependency, target, PackageId, metadata, or pack output changes, combine with ci-release-governance.
  9. Run targeted validation first, then broader solution or package validation when risk requires it.
  10. Review the full diff for unrelated modernization, formatting churn, project metadata drift, or weakened validation.
Show full SKILL.md (208 more words)Show less

Repository Baseline

  • Public packages currently target netstandard2.0.
  • The shared package version base is FluentMapPackageVersionPrefix in Directory.Build.props, with an explicit Version override in release workflows.
  • Package IDs currently include:
    • Dapper.FluentMap
    • Dapper.FluentMap.Dommel
    • FluentMap.DependencyInjection
    • FluentMap.Analyzers
    • FluentMap.Generators
  • Dependency versions are declared where the current project files declare them; this repository does not currently use Central Package Management.
  • Dapper.FluentMap.slnx is preferred for current SDK validation; Dapper.FluentMap.sln remains a compatibility fallback.

Validation

Use the commands from AGENTS.md that match the risk. As a starting point:

bash
dotnet restore ./Dapper.FluentMap.slnx
dotnet build ./Dapper.FluentMap.slnx --configuration Release --no-restore
dotnet test ./Dapper.FluentMap.slnx --configuration Release --no-build

When package output, metadata, dependency ranges, targets, or release compatibility are affected, also run pack validation using the actual eng scripts documented in AGENTS.md.

Restrictions

  • Do not change PackageId, targets, dependency ranges, authors, license, URLs, Source Link/provenance, or package readme/icon behavior without explicit scope.
  • Do not add package-management systems, lock-file policy, source generators, analyzers, nullable, NativeAOT/trimming claims, or SDK upgrades as incidental work.
  • Do not make internals public just for tests.
  • Do not reduce warnings, tests, analyzers, audit, or package validation to get a green run.
  • Do not publish packages, create tags, or trigger releases unless explicitly requested.

Quality Bar

A good library change resolves the requested behavior with a focused diff, preserves unrelated contracts, tests the relevant observable behavior, and keeps build/test/pack expectations consistent with the repository baseline.

© 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-library-change of rodri-oliveira-dev/Dapper-FluentMap.

Open the folder on GitHubat commit 4f5a39f

Compare with similar skills

Dotnet Library Change 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 Library Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dotnet Library Change this skillrodri-oliveira-dev/Dapper-FluentMap453—~1.1kAutomated safety check: PassMIT
Add Refactoringdotnet/roslynator3.5k—~946Automated safety check: PassCustom licence
.NET Native AOT Compatibilitydotnet/skills5.6k2 repos~4.2kAutomated safety check: PassMIT
Dynamo Dotnet ExpertDynamoDS/Dynamo2k—~922Automated safety check: PassApache-2.0
Roslynkmrpmorris/Roslynk128—~3.1kAutomated safety check: PassMIT
Deprecate Analyzer Or Refactoringdotnet/roslynator3.5k—~511Automated safety check: PassCustom licence

Similar skills

  • Add Refactoring

    dotnet/roslynator

    Official

    A skill your agent uses when adding a new RR refactoring in roslynator, editing Refactorings.xml, registering in RefactoringContext, or when refactorings-testing.md shows XunitRefactoringVerifier —…

    3.5k GitHub stars~946 tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • .NET Native AOT Compatibility

    dotnet/skills

    Official

    Makes .NET projects compatible with Native AOT and trimming by resolving IL trim and AOT analyzer warnings through annotations rather than suppressions.

    5.6k GitHub starsUsed in 2 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Dynamo Dotnet Expert

    DynamoDS/Dynamo

    Write and review C/.NET code in Dynamo following Dynamo coding standards, modern C patterns, and repo conventions.

    2k GitHub stars~922 tokensUpdated today
    DevelopmentAuto-check passed

  • Roslynk

    mrpmorris/Roslynk

    How to use the Roslynk MCP tools (mcproslynk) effectively for .NET work.

    128 GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Deprecate Analyzer Or Refactoring

    dotnet/roslynator

    Official

    A skill your agent uses when obsoleting or retiring RCS, RR, or RCF in roslynator, replacing an analyzer with another id, or when tempted to use IsObsolete on an Analyzer entry — analyzers use…

    3.5k GitHub stars~511 tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Okojo Test262

    akeit0/okojo

    Run and continue Okojo Test262 compliance work. An agent skill from akeit0/okojo.

    160 GitHub stars~742 tokensUpdated 18 days ago
    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.

    453 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Microbenchmarking

    rodri-oliveira-dev/Dapper-FluentMap

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

    453 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Nuget Trusted Publishing

    rodri-oliveira-dev/Dapper-FluentMap

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

    453 GitHub stars~1.3k tokensUpdated yesterday
    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…

    453 GitHub stars~1.5k tokensUpdated yesterday
    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.

    453 GitHub stars~1.1k tokensUpdated yesterday
    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.

    453 GitHub stars~750 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Dotnet Library Change

What does Dotnet Library Change do?

A skill your agent uses when changing Dapper-FluentMap production code, public contracts, project files, PackageIds, package metadata, dependencies, or related tests. Dotnet Library Change is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Use this skill when changing Dapper-FluentMap production code, public contracts, project files, PackageIds, package metadata, dependencies, or related tests.

When should I use Dotnet Library Change?

Dotnet Library Change fits situations like: changing Dapper-FluentMap production code; public contracts; package metadata; pure CI/release work.

How do I install Dotnet Library Change in Claude Code?

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

How do I install Dotnet Library Change in Codex?

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

Can I use Dotnet Library Change 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-library-change -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-library-change, .gemini/skills/dotnet-library-change, .github/skills/dotnet-library-change and .opencode/skills/dotnet-library-change in your project.

What does Dotnet Library Change need to run?

Going by SKILL.md and its folder, Dotnet Library Change needs the command-line tools its instructions call (dotnet).

Does Dotnet Library Change 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 Library Change 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 Library Change use?

Dotnet Library Change 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 Library Change use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Library Change?

Skills that share tags, products or a category with Dotnet Library Change: Add Refactoring (dotnet/roslynator, 3.5k stars), .NET Native AOT Compatibility (dotnet/skills, 5.6k stars), Dynamo Dotnet Expert (DynamoDS/Dynamo, 2k stars) and Roslynk (mrpmorris/Roslynk, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dotnet Library Change?

rodri-oliveira-dev (a GitHub user) maintains it in rodri-oliveira-dev/Dapper-FluentMap, which has 453 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.