MCPInstall

servicing-pr

by dotnetCode Quality & Workflow

Create EF Core PRs targeting servicing release branches (release/). Use when working on a PR that targets a release branch, backporting a fix from main, or when the user mentions servicing, patch, or release branch.

Installs
47
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/dotnet/efcore --skill servicing-pr
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads servicing-pr automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Servicing PRs

PRs targeting release/* branches require a specific description format and should include a quirk (AppContext switch) when applicable. When updating progress on a servicing PR, ensure that the description still follows the template.

Backport Target Branch

  • If a version is specified, target release/XX.0 (e.g., backport to 10 → release/10.0)
  • Otherwise, find the latest release/XX.0 branch (ignore preview branches like release/11.0-preview2)
  • Verify the branch exists before creating the PR

PR Title

[release/XX.0] <original PR title>

PR Description Template

Fixes #{issue_number}
Backports #{source_pr_number_if_applicable}

**Description**
Provide information on the bug, why it occurs and how it was introduced. Put it in terms that developers can understand without knowledge of EF Core internals.

**Customer impact**
How the bug affects users without internal technical detail. Include a short (3-4 lines) code sample if possible. If data corruption occurs, state that explicitly. If a feasible workaround exists, briefly describe it and how discoverable it is, otherwise mention that there's no workaround.

**How found**
How the bug was discovered based on the information in the issue description. If user-reported, mention "User reported on <version>". If multiple users are affected, note that. Count the number of upvotes and comment authors to estimate impact.

**Regression**
Whether this is a regression from an earlier EF version. Add a link to the PR that introduced the regression if known. If it only affects a feature introduced in the same major version, it is not a regression.

**Testing**
State the number of new or modified tests, don't go into details. If test coverage is unfeasible, briefly explain the alternative validation approach that was used.

**Risk**
Brief risk assessment ranked from "extremely low" to "high". Note amount of code changed. If the fix is a one-liner, mention that. If a quirk was added, mention "Quirk added".

Quirk (AppContext Switch)

A quirk lets users opt out of the fix at runtime, reducing patch risk. Skip when the fix is 100% obvious/risk-free, or when the quirk couldn't be used, like in tools or analyzers.

Adding a Quirk

Add in the class(es) containing code changes:

private static readonly bool UseOldBehavior37585 =
    AppContext.TryGetSwitch("Microsoft.EntityFrameworkCore.Issue37585", out var enabled) && enabled;
  • Change 37585 to the relevant issue number
  • Wrap changes with a condition on !UseOldBehavior37585 so activating the switch bypasses the fix, prefer to minimize the number of times the switch is checked
  • If the PR closes multiple issues, pick the most appropriate one for the switch name
  • Distinguish a recommendation from the staged implementation. Do not say "Quirk added" unless the source change actually includes the switch.

Validation

  • PR description follows the template completely (all sections filled)
  • Quirk added where appropriate with issue number matching the PR description

FAQ

What does the servicing-pr skill do?

Create EF Core PRs targeting servicing release branches (release/). Use when working on a PR that targets a release branch, backporting a fix from main, or when the user mentions servicing, patch, or release branch.

How do I install servicing-pr?

Run npx skills add https://github.com/dotnet/efcore --skill servicing-pr in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/servicing-pr/ (personal) or .claude/skills/servicing-pr/ (project).

Which AI agents can use servicing-pr?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is servicing-pr safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains servicing-pr?

It is published by dotnet in dotnet/efcore. It has 47 recorded installs.

More from dotnet/efcore

View all →

migrations

dotnet/efcore

Implementation details for EF Core migrations. Use when changing MigrationsSqlGenerator, model diffing, migration operations, HistoryRepository, the Migrator or related classes.

Backend & APIs61 installs

model-building

dotnet/efcore

Implementation details for EF Core model building. Use when changing ConventionSet, ModelBuilder, IConvention implementations, ModelRuntimeInitializer, RuntimeModel, or related classes.

Backend & APIs54 installs

tooling

dotnet/efcore

Implementation details for the EF Core dotnet-ef CLI and tooling. Use when changing dotnet-ef commands, the ef wrapper, EFCore.Tools (PMC), or EFCore.Tasks MSBuild integration.

Backend & APIs53 installs

update-pipeline

dotnet/efcore

Open the skill to read its SKILL.md instructions.

Backend & APIs52 installs

change-tracking

dotnet/efcore

Implementation details for EF Core change tracking. Use when changing InternalEntityEntry, ChangeDetector, SnapshotFactoryFactory, or related entity state, snapshot, or property accessor code.

Backend & APIs48 installs

sqlite-adonet

dotnet/efcore

Implementation details for the Microsoft.Data.Sqlite ADO.NET provider. Use when changing files under src/Microsoft.Data.Sqlite.Core/.

Data & Databases48 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Code Quality & Workflow1.4M installs

improve-codebase-architecture

mattpocock/skills

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Code Quality & Workflow1.2M installs

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

Code Quality & Workflow1.1M installs

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

Code Quality & Workflow890.6K installs

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Code Quality & Workflow863.8K installs

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Code Quality & Workflow848.4K installs