New: 98,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

PR Authoring

by symfony in symfony/symfony

Hold your own work to the review standard of this repository, so that a change is merge-ready when it is opened.

MITAuto-check passedDevelopment

Install PR Authoring

skills CLI
$ npx skills add symfony/symfony --skill pr-authoring -a claude-code

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

GitHub CLI
$ gh skill install symfony/symfony pr-authoring --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/symfony/symfony.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-authoring .claude/skills/pr-authoring && 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
pr-authoring
GitHub stars
31k
Token cost
~1.5k tokens
SKILL.md length
923 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Hold your own work to the review standard of this repository, so that a change is merge-ready when it is opened.

  • The user asks to fix an issue
  • SKILL.md covers Consult the review standard…, Before writing code, While working and Running the tests, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Make any other change to this codebase

What it does

PR Authoring is an agent skill from symfony/symfony. Hold your own work to the review standard of this repository, so that a change is merge-ready when it is opened. Use when the user asks to fix an issue, to add a feature, to refactor, or to make any other change to this codebase, and read it before writing the first line of code.

Its SKILL.md is about 1.5k 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. It works with Symfony and PHP. The repository describes itself as: The Symfony PHP framework. The licence is MIT.

When your agent uses it

  • The user asks to fix an issue
  • Make any other change to this codebase
  • Read it before writing the first line of code

Example prompts

  • “/pr-authoring”

What it can do on your machine

Read from SKILL.md and the folder at commit 42be462. 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

PR Authoring loads about 1.5k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 923 words of instructions outside code blocks.

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

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 symfony/symfony at commit 42be462, republished under its MIT licence (© symfony). 923 words, ~1,473 tokens.

Download SKILL.mdSave it as .claude/skills/pr-authoring/SKILL.md (or your agent's skills folder).
name
pr-authoring
description
Hold your own work to the review standard of this repository, so that a change is merge-ready when it is opened. Use when the user asks to fix an issue, to add a feature, to refactor, or to make any other change to this codebase, and read it before writing the first line of code.

Authoring a pull request

Consult the review standard first

  • Read .agents/skills/pr-review-merge-prep/SKILL.md in full before writing code. It states what a change must satisfy to be merged here.
  • That skill speaks from the reviewer's seat, and every requirement in it applies to the code you write yourself. A reviewer will hold your pull request to it, so hold your work to it first.
  • This skill says when to consult the review skill and what to do with the answer. It repeats only the rules that apply to every keystroke, listed under House rules below, so that they hold even before that skill is open. When the two seem to disagree, the review skill decides.

Before writing code

  • Choose the target branch before the first commit, with the branch rules of the review skill. The target decides which APIs the code may use, which test style it follows, and where the changelog entry goes. Changing it later means rewriting the change, not rebasing it.
  • Re-derive the problem from the code, whatever the issue or the request says it is. A report describes a symptom. Work from the cause you found yourself.
  • Reproduce the current behavior with a probe or a failing test before changing anything. A fix for a problem you never saw happen cannot be verified.
  • Run the public-API challenge of the review skill against your own design before you build it, not after. Dropping a method that is not needed costs nothing at that point. Defending one that is not justified costs a whole discussion later.

While working

  • Keep the diff to what the request needs. Unrelated cleanups make the change harder to review, and they can pull it toward another target branch. Report what you find outside that scope, or send it as its own pull request.
  • Apply the house rules of the review skill to everything you produce: tests first, comments, tone, attribution, order of methods, plain English.

Running the tests

  • Run one component at a time, by path: ./phpunit src/Symfony/Component/<Name>, and the same form for src/Symfony/Bridge/<Name> and src/Symfony/Bundle/<Name>. Everything under src/Symfony/Contracts is a single suite: ./phpunit src/Symfony/Contracts.
  • Never run the whole monorepo at once. It takes hours, and it buries the failure you are looking for.
  • Narrow to one test file or one filter while iterating, then run the full suite of every touched component before calling the change done.
  • Read the summary line, not the exit status alone. A run can end with Tests: N, Failures: 1, or die on a fatal error before any banner, and colour codes sit in front of those words.
  • After every rebase or merge, rerun the tests of the patched components. A replay that raised no conflict still produces broken code. Run the rebase or merge itself non-interactively, with GIT_EDITOR=true.
Show full SKILL.md (463 more words)Show less

Before opening it

  • Review your own diff with the review skill, as if someone else had written it. Run the checks it asks a reviewer to run: revert-verify each new test, probe the edge cases, check every borrowed symbol against the declared version constraints, check that the changelog and upgrade entries sit in the unreleased section, and run the full suite of every touched component together with the style tool.
  • Apply what that pass finds. Do not file the findings in the description as known limitations, because a reviewer reads them as work left undone.
  • Shape the commits before pushing: a message that matches its diff, and a structure that carries meaning, such as a failing test followed by the fix.
  • Write the description for someone who never saw the request: what the change does, the public API it adds, the options and their defaults, and the traps. Fill the header table, and give the title the component prefix.
  • Say which checks you ran and what they returned. State what you did not cover just as plainly.
  • A change on a maintained branch gets merged up. When a higher branch needs a different shape, end the description with a Merge-up to <branch>: paragraph giving the declarations to add, the style that branch expects, or the resolved code itself, and say whether you ran it there. The merge-up skill reads those paragraphs back out of the merge commit, so writing one saves the merger from rediscovering the resolution.

Opening it

  • Opening a pull request, pushing to it and commenting on it are outward actions. Ask the user before the first one, unless they already asked for the pull request.
  • Push the branch to a fork. Never push a working branch to the upstream repository.

House rules

These hold whether or not the review skill is open, and they cover inherited content too, such as a commit you amend or a patch you rebase.

  • Use TDD: the failing test comes first, the implementation second, the full suite of the touched component last.
  • Write code comments sparingly, only where they add value the code cannot express. A test method or a test helper carries no docblock and no comment narrating it: its name and its assertions say what it checks. The comment that stays in a test is the one saying why a fixture looks wrong on purpose. Never reference an issue or a pull request from code or from tests.
  • No em-dashes. No Co-Authored-By trailer. No credit to Claude, to Anthropic or to any other AI tool, anywhere: code, commit messages, pull request titles and bodies, review comments, issue comments.
  • Keep a factual tone in everything published, and use plain English: common words, short sentences, one idea per sentence. Most readers are not native speakers.

© symfony, 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/pr-authoring of symfony/symfony.

Open the folder on GitHubat commit 42be462

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in symfony/symfony, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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

PR Authoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Authoring this skillsymfony/symfony31k—~1.5kAutomated safety check: PassMIT
Clean Architecturegiuseppe-trisciuoglio/developer-kit355—~4.2kAutomated safety check: NotesMIT
PHP ProJeffallan/claude-skills12k—~1.6kAutomated safety check: NotesMIT
Shopware CLI Dockershopware/shopware-cli123—~1.8kAutomated safety check: PassMIT
Sentry Php SDKgetsentry/sentry-for-ai268—~3.7kAutomated safety check: NotesApache-2.0
Php ProAratKruglik/claude-laravel155—~984Automated safety check: NotesNone

Similar skills

  • Clean Architecture

    giuseppe-trisciuoglio/developer-kit

    Provides implementation patterns for Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design in PHP 8.3+ with Symfony 7.x.

    355 GitHub stars~4.2k tokensUpdated 28 days ago
    DevelopmentAuto-check: notes

  • PHP Pro

    Jeffallan/claude-skills

    Writes strictly typed modern PHP 8.3+ for Laravel, Symfony and plain projects, with PHPStan level 9, PHPUnit or Pest tests, typed DTOs and secure defaults.

    12k GitHub stars~1.6k tokensUpdated 5 days ago
    Backend & APIsAuto-check: notes

  • Shopware CLI Docker

    shopware/shopware-cli

    A skill your agent uses when working on Docker-backed Shopware projects and needing to run Shopware or Symfony CLI commands, interact with project services or databases, start or stop the…

    123 GitHub stars~1.8k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Sentry Php SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for PHP. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~3.7k tokensUpdated yesterday
    Backend & APIsAuto-check: notes

  • Php Pro

    AratKruglik/claude-laravel

    A skill your agent uses when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks.

    155 GitHub stars~984 tokensUpdated 5 mo ago
    Backend & APIsAuto-check: notes

  • Php Symfony Audit

    0xShe/PHP-Code-Audit-Skill

    Symfony 框架特效安全审计工具。针对 Symfony 常见 security.yaml、CSRF、Twig/Twig raw、表达式与访问控制等框架机制做白盒静态审计，并将风险映射到通用漏洞类型体系（AUTH/CSRF/CFG/XSS/TPL/LOGIC 等）。

    402 GitHub starsUsed in 1 repo~599 tokens
    SecurityAuto-check passed

More from symfony/symfony

All 9 skills in this repo

  • Sync Translations

    symfony/symfony

    Synchronize translation catalogs across maintained Symfony branches: find messages that newer branches added to the English catalogs but that are still missing from the oldest maintained branch…

    31k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Bug Triage

    symfony/symfony

    Decide whether open Bug PRs target the correct branch. An agent skill from symfony/symfony.

    31k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Merge Up

    symfony/symfony

    Cascade-merge maintained Symfony branches from oldest to newest (e.g.

    31k GitHub stars~4k tokensUpdated yesterday
    Auto-check passed

  • PR Merge

    symfony/symfony

    Merge a reviewed pull request the way the Symfony core team does: one --no-ff merge commit per PR, whose message archives the whole discussion, with the review gates checked first.

    31k GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Security Triage

    symfony/symfony

    Triage a reported security finding into a disposition: a private CVE (coordinated disclosure + advisory), a public hardening PR (fix in the open, no CVE), or not-a-security-issue (reply to reporter).

    31k GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

  • Symfony Security Review

    symfony/symfony

    Review a change (a PR, the current branch diff, or a set of files) or audit a component or the whole tree for missing or incorrect security hardening.

    31k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about PR Authoring

What does PR Authoring do?

Hold your own work to the review standard of this repository, so that a change is merge-ready when it is opened. PR Authoring is an agent skill from symfony/symfony. Hold your own work to the review standard of this repository, so that a change is merge-ready when it is opened.

When should I use PR Authoring?

PR Authoring fits situations like: the user asks to fix an issue; make any other change to this codebase; read it before writing the first line of code.

How do I install PR Authoring in Claude Code?

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

How do I install PR Authoring in Codex?

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

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

What does PR Authoring need to run?

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

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

PR Authoring 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 PR Authoring use?

About 1.5k tokens (SKILL.md is roughly 5.9k 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 PR Authoring?

Skills that share tags, products or a category with PR Authoring: Clean Architecture (giuseppe-trisciuoglio/developer-kit, 355 stars), PHP Pro (Jeffallan/claude-skills, 12k stars), Shopware CLI Docker (shopware/shopware-cli, 123 stars) and Sentry Php SDK (getsentry/sentry-for-ai, 268 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Authoring?

symfony (a GitHub organization) maintains it in symfony/symfony, which has 31,183 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

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