Prepare the PR

Automate standardized pull request creation for sample contributions with branch naming and labels.

25|8|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/microsoft/Employee-Self-Service-Agent-Developer-Kit --skill prepare-the-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Prepare the PR
Source: https://github.com/microsoft/Employee-Self-Service-Agent-Developer-Kit/tree/main/.github/agents/skills/prepare-sample-pr
Command: npx skills add https://github.com/microsoft/Employee-Self-Service-Agent-Developer-Kit --skill prepare-the-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the inconsistency and manual effort of formatting sample contribution pull requests to match the repository's strict branch naming, commit message, PR template, and labeling requirements, reducing review friction and integration delays for sample updates.

Core Features & Use Cases

  • Standardized Branch Naming: Automatically generates compliant branch names tied to issue numbers and kebab-case slugs derived from issue titles.
  • Consistent PR Metadata: Enforces the correct commit message and PR title format (samples(<Area>/<Topic>): <summary> (#<issue-number>)) and provides a pre-filled PR body template with all required sections.
  • Built-in Guardrails: Enforces contribution rules like one issue per PR, required labels (area:samples, agent:eligible), and stop conditions to prevent invalid PRs from being opened.
  • Use Case: A contributor submitting a new sample topic for the Facilities area can use this Skill to instantly generate a compliant PR linked to the tracking issue, with all required metadata and labels applied automatically.

Quick Start

Use the prepare-sample-pr skill to create a properly formatted pull request for your sample contribution linked to your open GitHub issue.

Frequently Asked Questions about Prepare the PR

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a standardized pull request for sample contributions?

To format sample contribution pull requests, this Skill automatically generates compliant branch names, enforces commit message formats, and applies required labels. It eliminates manual formatting effort and ensures strict adherence to repository contribution rules.

What is the correct commit message format for sample pull requests?

The correct commit message format for sample pull requests is `samples(<Area>/<Topic>): <summary> (#<issue-number>)`. This Skill automatically enforces this metadata convention to maintain consistency across sample contribution integrations.

How do I generate a branch name tied to a GitHub issue for my PR?

To generate a branch name tied to a GitHub issue, this Skill derives a kebab-case slug from the issue title and links it to the issue number. This ensures branch naming conventions are met for sample contributions.

What are the required labels for submitting a sample contribution PR?

The required labels for submitting a sample contribution PR are `area:samples` and `agent:eligible`. This Skill applies these labels automatically as a built-in guardrail to prevent invalid pull requests from being opened.

Can I submit multiple GitHub issues in a single sample contribution PR?

You cannot submit multiple GitHub issues in a single sample contribution PR. This Skill enforces a strict one issue per PR contribution rule with stop conditions to prevent invalid pull requests from being created.

Does this PR automation work for the Employee Self-Service Agent repository?

This PR automation works specifically for the Employee Self-Service Agent repository. It streamlines sample updates by enforcing contribution rules and consistent PR metadata tailored to that repository's integration workflow.