New: 97,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 Issue Implementation

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

A skill your agent uses to turn a well-defined issue into a small Dapper-FluentMap library change with requirements, implementation, tests, validation, and Definition of Done traceability.

MITAuto-check passedDevelopment

Install Dotnet Issue Implementation

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

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

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

At a glance

A skill your agent uses to turn a well-defined issue into a small Dapper-FluentMap library change with requirements, implementation, tests, validation, and Definition of Done traceability.

  • Works in 10 steps: Read root AGENTS.md, then the full issue… → Extract the problem, expected behavior,… → Search before opening large files.… → …
  • Turn a well-defined issue into a small Dapper-FluentMap library change with requirements
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Definition of Done traceability

What it does

Dotnet Issue Implementation is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Use this skill to turn a well-defined issue into a small Dapper-FluentMap library change with requirements, implementation, tests, validation, and Definition of Done traceability. Do not use for open-ended bug investigation or PR review.

Its SKILL.md is about 780 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

  • Turn a well-defined issue into a small Dapper-FluentMap library change with requirements
  • Definition of Done traceability
  • Open-ended bug investigation

Example prompts

  • “/dotnet-issue-implementation”

Workflow steps

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

  1. Read root AGENTS.md, then the full issue or user-provided requirements.
  2. Extract the problem, expected behavior, constraints, Definition of Done, non-goals, and ambiguities.
  3. Search before opening large files. Locate only the relevant contracts, implementation, tests, package metadata, docs, and workflows.
  4. Identify the affected package(s): core, Dommel, DependencyInjection, Analyzers, Generators, tests, benchmarks, docs, or CI/release.
  5. Check whether the change affects public API, source/binary/behavior compatibility, Dapper integration, global state/cache behavior…
  6. Choose the smallest implementation that satisfies the issue without opportunistic modernization.
  7. Add or update tests for behavior changes. For bugs, prefer a regression test that fails before the fix when practical.
  8. Update README.md, COMPATIBILITY.md, MIGRATION.md, XML docs, or CHANGELOG.md only when the consumer-facing contract changes.
  9. Run the nearest validation from AGENTS.md; broaden to solution or package validation only when the risk warrants it.
  10. Review the complete diff and mark each DoD item as satisfied, blocked, or not applicable.

What it can do on your machine

Read from SKILL.md and the folder at commit 90600cb. 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 Issue Implementation loads about 780 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 365 words of instructions outside code blocks.

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

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 90600cb, republished under its MIT licence (© rodri-oliveira-dev). 365 words, ~780 tokens.

Download SKILL.mdSave it as .claude/skills/dotnet-issue-implementation/SKILL.md (or your agent's skills folder).
name
dotnet-issue-implementation
description
Use this skill to turn a well-defined issue into a small Dapper-FluentMap library change with requirements, implementation, tests, validation, and Definition of Done traceability. Do not use for open-ended bug investigation or PR review.
license
MIT

Purpose

Implement a defined issue end to end without expanding scope, while preserving Dapper-FluentMap's public contracts, package boundaries, compatibility promises, and release safety.

Process

  1. Read root AGENTS.md, then the full issue or user-provided requirements.
  2. Extract the problem, expected behavior, constraints, Definition of Done, non-goals, and ambiguities.
  3. Search before opening large files. Locate only the relevant contracts, implementation, tests, package metadata, docs, and workflows.
  4. Identify the affected package(s): core, Dommel, DependencyInjection, Analyzers, Generators, tests, benchmarks, docs, or CI/release.
  5. Check whether the change affects public API, source/binary/behavior compatibility, Dapper integration, global state/cache behavior, dependencies, package output, or release flow.
  6. Choose the smallest implementation that satisfies the issue without opportunistic modernization.
  7. Add or update tests for behavior changes. For bugs, prefer a regression test that fails before the fix when practical.
  8. Update README.md, COMPATIBILITY.md, MIGRATION.md, XML docs, or CHANGELOG.md only when the consumer-facing contract changes.
  9. Run the nearest validation from AGENTS.md; broaden to solution or package validation only when the risk warrants it.
  10. Review the complete diff and mark each DoD item as satisfied, blocked, or not applicable.

Combine With

  • dotnet-library-change when production code, project files, dependencies, public contracts, or package metadata change.
  • dotnet-refactoring-engineer when the implementation includes behavior-preserving restructuring.
  • ci-release-governance when workflows, packaging, versioning, release, or recovery are involved.
  • dotnet-pr-review only when the task is to review an existing diff rather than implement it.
Show full SKILL.md (133 more words)Show less

Dapper-FluentMap Constraints

  • The default branch is main; do not implement on main.
  • Treat this as a public multi-package .NET library, not an application.
  • Do not assume project name, assembly name, namespace, path, and NuGet PackageId are the same identity.
  • Preserve netstandard2.0 for public packages unless the issue explicitly changes compatibility.
  • Keep core focused on mapping; do not add ORM, CRUD, SQL generation, migrations, or connection abstractions as incidental scope.
  • Do not publish, tag, release, or push unless explicitly requested by the user.

Expected Output

Report what changed, main files, validation commands and results, DoD status, compatibility impact, and remaining risks or blockers.

Quality Bar

A good issue implementation satisfies the stated DoD with the smallest coherent diff, tests the relevant observable behavior, preserves unrelated contracts, and leaves validation evidence proportional to the risk.

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

Open the folder on GitHubat commit 90600cb

Compare with similar skills

Dotnet Issue Implementation 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 Issue Implementation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dotnet Issue Implementation this skillrodri-oliveira-dev/Dapper-FluentMap453—~780Automated safety check: PassMIT
MAUI PR Performance Analysisdotnet/maui23k—~2.4kAutomated safety check: PassMIT
Code Reviewjonathanpeppers/dotnes780—~2.1kAutomated safety check: PassMIT
Open Pull RequestGremlinq/ExRam.Gremlinq187—~1.5kAutomated safety check: PassMIT
Pull RequestOpenCoreMMO/OpenCoreMMO481—~814Automated safety check: PassGPL-3.0
Gh Stackdotnet/macios2.9k2 repos~10kAutomated safety check: PassCustom licence

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 14 days ago
    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 2 days ago
    DevelopmentAuto-check passed

  • Pull Request

    OpenCoreMMO/OpenCoreMMO

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

    481 GitHub stars~814 tokensUpdated 15 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 2 repos~10k tokens
    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 2 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 Issue Implementation

What does Dotnet Issue Implementation do?

A skill your agent uses to turn a well-defined issue into a small Dapper-FluentMap library change with requirements, implementation, tests, validation, and Definition of Done traceability. Dotnet Issue Implementation is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Use this skill to turn a well-defined issue into a small Dapper-FluentMap library change with requirements, implementation, tests, validation, and Definition of Done traceability.

When should I use Dotnet Issue Implementation?

Dotnet Issue Implementation fits situations like: turn a well-defined issue into a small Dapper-FluentMap library change with requirements; definition of Done traceability; open-ended bug investigation.

How do I install Dotnet Issue Implementation in Claude Code?

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

How do I install Dotnet Issue Implementation in Codex?

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

Can I use Dotnet Issue Implementation 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-issue-implementation -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-issue-implementation, .gemini/skills/dotnet-issue-implementation, .github/skills/dotnet-issue-implementation and .opencode/skills/dotnet-issue-implementation in your project.

What does Dotnet Issue Implementation need to run?

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

Does Dotnet Issue Implementation 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 Issue Implementation 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 Issue Implementation use?

Dotnet Issue Implementation 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 Issue Implementation use?

About 780 tokens (SKILL.md is roughly 3.1k 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 Issue Implementation?

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

Who maintains Dotnet Issue Implementation?

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 6, 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.