Official agent skill

Servicing PR

by dotnet in dotnet/efcore

Create EF Core PRs targeting servicing release branches (release/).

OfficialMITAuto-check passed

Install Servicing PR

skills CLI
$ npx skills add dotnet/efcore --skill servicing-pr -a claude-code

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

GitHub CLI
$ gh skill install dotnet/efcore servicing-pr --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/dotnet/efcore.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/servicing-pr .claude/skills/servicing-pr && 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
servicing-pr
GitHub stars
15k
Token cost
~833 tokens
SKILL.md length
212 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Create EF Core PRs targeting servicing release branches (release/).

  • Working on a PR that targets a release branch
  • SKILL.md covers Backport Target Branch, PR Title, PR Description Template and Quirk (AppContext Switch), plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Backporting a fix from main

What it does

Servicing PR is an agent skill from dotnet/efcore, published by the product's own GitHub organization. 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.

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

The repository describes itself as: EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations. The licence is MIT.

When your agent uses it

  • Working on a PR that targets a release branch
  • Backporting a fix from main
  • The user mentions servicing

Example prompts

  • “/servicing-pr”

What it can do on your machine

Read from SKILL.md and the folder at commit d2f4410. 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 (its code samples are csharp).

    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

Servicing PR loads about 833 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 212 words of instructions outside code blocks.

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

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 dotnet/efcore at commit d2f4410, republished under its MIT licence (© dotnet). 212 words, ~833 tokens.

Download SKILL.mdSave it as .claude/skills/servicing-pr/SKILL.md (or your agent's skills folder).
name
servicing-pr
description
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.

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:

csharp
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

© dotnet, 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/servicing-pr of dotnet/efcore.

Open the folder on GitHubat commit d2f4410

Compare with similar skills

Servicing PR 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.

Servicing PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Servicing PR this skilldotnet/efcore15k—~833Automated safety check: PassMIT
Shepherd PRsflutter/flutter179k—~1.7kAutomated safety check: PassBSD-3-Clause
Railway Servicedavila7/claude-code-templates32k—~1.7kAutomated safety check: PassMIT
Branchesredis/RedisInsight8.9k—~409Automated safety check: PassCustom licence
Conventional Branchgithub/awesome-copilot40k—~1.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Shepherd PRs

    flutter/flutter

    Automate shepherding, checking status, updating branches, and landing open PRs or approved third-party contributor PRs in the flutter/flutter repository using the gh CLI.

    179k GitHub stars~1.7k tokensUpdated today
    MobileAuto-check passed
  • Railway Service

    davila7/claude-code-templates

    Check service status, rename services, change service icons, link services, or create services with Docker images.

    32k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Branches

    redis/RedisInsight

    Official

    Create and name git branches following project conventions. An agent skill from redis/RedisInsight.

    8.9k GitHub stars~409 tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Conventional Branch

    github/awesome-copilot

    Official

    Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/).

    40k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    61k GitHub stars~594 tokensUpdated today
    DevelopmentAuto-check passed

More from dotnet/efcore

All 17 skills in this repo
  • Make Skill

    dotnet/efcore

    Official

    Create and evaluate new Agent Skills for GitHub Copilot. An agent skill from dotnet/efcore.

    15k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Make Custom Agent

    dotnet/efcore

    Official

    Create custom GitHub Copilot agents. An agent skill from dotnet/efcore.

    15k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Official

    Create GitHub Actions workflows for CI, automation, or PR management.

    15k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Make Instructions

    dotnet/efcore

    Official

    Create and evaluate VS Code file-based instructions (.instructions.md files).

    15k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Model Building

    dotnet/efcore

    Official

    Implementation details for EF Core model building. An agent skill from dotnet/efcore.

    15k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Run Apichief

    dotnet/efcore

    Official

    Run ApiChief in the EF Core repo to emit baselines, summaries, deltas, review files, or breaking-change checks.

    15k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Questions about Servicing PR

What does Servicing PR do?

Create EF Core PRs targeting servicing release branches (release/). Servicing PR is an agent skill from dotnet/efcore, published by the product's own GitHub organization. Create EF Core PRs targeting servicing release branches (release/).

When should I use Servicing PR?

Servicing PR fits situations like: working on a PR that targets a release branch; backporting a fix from main; the user mentions servicing.

How do I install Servicing PR in Claude Code?

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

How do I install Servicing PR in Codex?

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

Can I use Servicing PR 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 dotnet/efcore --skill servicing-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/servicing-pr, .gemini/skills/servicing-pr, .github/skills/servicing-pr and .opencode/skills/servicing-pr in your project.

What does Servicing PR need to run?

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

Does Servicing PR 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 Servicing PR 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 Servicing PR use?

Servicing PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Servicing PR use?

About 833 tokens (SKILL.md is roughly 3.3k 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 Servicing PR?

Skills that share tags, products or a category with Servicing PR: Shepherd PRs (flutter/flutter, 179k stars), Railway Service (davila7/claude-code-templates, 32k stars), Branches (redis/RedisInsight, 8.9k stars) and Conventional Branch (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Servicing PR?

dotnet (a GitHub organization, an official publisher) maintains it in dotnet/efcore, which has 14,800 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.

Source: dotnet/efcore on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.