agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/Employee-Self-Service-Agent-Developer-Kit/.github/agents/skills/prepare-sample-pr/SKILL.md

prepare-sample-pr

Skill29 starsChanged 6 months agoMITView on GitHub

Preconditions: all validate-sample-topic checks PASS. <short-slug> is a kebab-case 2–5 word summary derived from the issue title. Same as the commit message.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Do not enable auto-merge.

    line 50
  2. Distinctive:

    Do not request reviewers automatically — leave for humans / CODEOWNERS.

    line 51
  3. Distinctive:

    Do not force-push after a human has reviewed.

    line 52
  4. Distinctive:

    Stop if the diff is empty.

    line 57
  5. Distinctive:

    Stop if the branch name or PR title cannot be derived from the issue.

    line 58

≈ “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

Skill: Prepare the PR

Preconditions: all validate-sample-topic checks PASS.

Branch

agent/samples/issue-<issue-number>-<short-slug>

<short-slug> is a kebab-case 2–5 word summary derived from the issue title.

Commit message

samples(<Area>/<Topic>): <short summary> (#<issue-number>)

Examples:

  • samples(Facilities/EmployeeInviteGuest): tighten modelDescription wording (#123)
  • samples(Workday/Employee/EmployeeGetVacationBalance): fix date handling (#124)

PR title

Same as the commit message.

PR body template

## Summary
<one paragraph tied to the issue>

## Changes
- <bullet list of files added/changed>

## Reference topic used
<path to the neighbor topic used as shape reference>

## Validation
<paste the validation summary block from validate-sample-topic>

## Linked issue
Fixes #<issue-number>

Rules

  • One issue → one PR.
  • Do not enable auto-merge.
  • Do not request reviewers automatically — leave for humans / CODEOWNERS.
  • Do not force-push after a human has reviewed.
  • Apply labels: area:samples and agent:eligible.

Stop conditions

  • Stop if the diff is empty.
  • Stop if the branch name or PR title cannot be derived from the issue.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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