Borrowing it
Nothing to install: this file belongs to pplancq/copilot-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pplancq/copilot-instructions/main/.github/skills/pr-description/SKILL.mdgit clone --depth 1 https://github.com/pplancq/copilot-instructionsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pplancq/copilot-instructions/pr-description)<a href="https://agentmods.dev/skills/pplancq/copilot-instructions/pr-description"><img src="https://agentmods.dev/badge/skills/pplancq/copilot-instructions/pr-description/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pplancq/copilot-instructions/pr-description"><img src="https://agentmods.dev/badge/skills/pplancq/copilot-instructions/pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00084 | $0.04504 |
| Opus 5.5 | $0.00034 | $0.01802 |
| Sonnet 5.5 | $0.00017 | $0.00901 |
| Haiku 4.5 | $0.00008 | $0.00450 |
Grade A, and why
pr-description scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST \ How it starts
The opening of the file, as written. The whole thing — 560 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Description Generator
Automatically generate comprehensive pull request descriptions that follow the project's PR template (.github/PULL_REQUEST_TEMPLATE.md).
When to Use This Skill
Activate this skill when the user asks to:
- "Generate a PR" or "Create a PR"
- "Open a pull request"
- "Create pull request"
- "Generate a PR description"
- "Fill out the PR template"
- "Write a description for my changes"
Prerequisites
- Working git repository with commits on a feature branch
- Changes committed to the current branch
- Access to the project's
.github/PULL_REQUEST_TEMPLATE.mdtemplate
Main Branch Detection
The skill needs to identify the main branch to generate accurate diffs. Follow this priority:
- User-provided: If the user specifies the main branch name (e.g., "main", "master", "develop"), use it
- Project instructions: Check
.github/copilot-instructions.mdfor default branch configuration - Git default: Use
git symbolic-ref refs/remotes/origin/HEADto detect the default branch - Fallback: Default to "main" if detection fails
- Ask user: If uncertain, prompt the user to confirm the main branch name
Step-by-Step Workflow
Step 1: Get GitHub Issue Link
If the user hasn't provided a GitHub issue link, ask for it:
Prompt: "What is the GitHub issue link for this PR? (e.g., https://github.com/owner/repo/issues/123 or just #123)"
Accepted formats:
- Full URL:
https://github.com/owner/repo/issues/123 - Short format:
#123 - Just number:
123
Step 2: Read GitHub Issue
Use the GitHub MCP tools to read the issue content:
# Extract issue number from the link
# Then use GitHub API to read issue details
Extract from the issue:
- Title: Use as context for PR title
- Description: Understand the problem/feature request
- Acceptance criteria: Verify if changes align with expected outcome
- Labels: Determine type of change (bug, feature, enhancement)
- Related context: Any linked PRs, discussions, or references
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 560 lines · 84 tokens per session scan A a5234215d27c
pr-description is a skill published in the GitHub repository pplancq/copilot-instructions (4 stars, last pushed 8mo ago), licensed MIT. It adds 84 tokens to every session and 4,504 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…