MicrosoftKnown publishermicrosoft/webui/.github/skills/pr/SKILL.md

pr

Skill100 starsChanged 36 days agoMITView on GitHub

Guidance for branch naming, commit messages, and PR titles.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Never commit to main directly: Create a branch: <user>/<short-description> (e.g.
line 10
Very specific:
When a PR is meant to close a GitHub issue, include the keyword Closes followed by the issue number in the PR description body (not the …
line 31
Distinctive:
Remove the Co-author-by line from the PR description.
line 47

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Pull Request Conventions

Branch discipline

Never commit to main directly. Create a branch: <user>/<short-description> (e.g. mmansour/optimize-handler-allocs).
One logical change per commit. Write imperative messages: "Add …" not "Added …".

PR title format

PR titles must use a Conventional Commits prefix:

Prefix	When to use	Example
`feat:`	New feature or capability	`feat: add HTTP/2 support to hyper example`
`fix:`	Bug fix	`fix: render missing signals as empty`
`perf:`	Speed or memory improvement, measured	`perf: reduce allocations on hot paths`
`chore:`	Maintenance, refactoring, CI, docs, dependencies	`chore: move shared files to examples/app`

The prefix is lowercase, followed by a colon and a space, then a short imperative description.

A perf: PR must report before/after numbers in its description - see the perf skill for how to measure.

Linking PRs to issues

When a PR is meant to close a GitHub issue, include the keyword Closes followed by the issue number in the PR description body (not the title):

Closes #42

For multiple issues, use one per line:

Closes #42
Closes #43

Note: Issue-linking keywords only work when the PR targets the repository's default branch. See GitHub docs: linking a pull request to an issue for the full reference.

PR description

Remove the Co-author-by line from the PR description. If you want to credit a co-author, add them as a reviewer instead. And check all the changes from its merge-base to get a detailed summary for the commit.

Framework change PRs

For PRs touching core framework code (handler, parser, protocol, router, CLI runtime, FFI), apply the code-review skill checklist before opening the PR. It covers correctness, concurrency, performance, design, and style checks that complement the automated quality gate.

Download now (ZIP)

In this repository11 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- webui-referenceSkill
- bump-versionSkill
- code-reviewSkill
- create-exampleSkill
- diagnosticsSkill
- docs-syncSkill
- perfSkill
- quality-gateSkill
- testingSkill
- webui-devSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free