agentleFS
lutzseverinolutzseverino/repo-standards/.agents/skills/pr/SKILL.md

pr

Skill0 starsChanged 5 days agoMITView on GitHub

Use when writing a PR body.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this template for writing the PR body:

    line 14
  2. Distinctive:

    Keep the sections in this order.

    line 41
  3. Very specific:

    Use diff when the point is what changes and the surrounding shape already exists.

    line 94
  4. Distinctive:

    Place each visual next to the short text it supports.

    line 114

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

A prompt or brief naming this skill is its invocation.

Use this template for writing the PR body:

## Summary

<diagram, diff-sketch, or tree>

## Evidence

- **Before:** <screenshot/output/failing test run>
  **After:** <screenshot/output/passing test run>

## Merge Danger

**Door:** <one-way or two-way>

<optional: description>

**Blast Radius:** <one-word description>

<optional: potential ramifications of merge>

## Related issue

<closing or partial-work reference, or Direct change: reason>

Keep the sections in this order. Put any other material, such as scope, impact, or migration, in a subsection of the section it belongs to.

Sections

Skip all preambles and keep prose brief. Use the user's domain language from GLOSSARY.md.

Summary

Pick the smallest view that makes the key point clear.

  • Show logic or an algorithm as pseudocode:
on(save)
  if unchanged: return cached result
  write content
  return fresh result
  • Show runtime control flow as a call tree:
submitForm
  createSession
    launchAgent
  navigateToSession
  • Show UI structure as a component tree, including state and module boundaries that matter:
<SessionPage> (apps/example/src/routes/session.tsx)
  useSessionEvents()
  <RunSkillButton /> (packages/ui)
  • Show file responsibility or a broad refactor as a shallow file tree:
src/
├── commands/    # parses user actions
└── transport/   # sends API requests
  • Show component interaction, control flow, or data flow with Mermaid:
sequenceDiagram
    User->>UI: choose command
    UI->>Daemon: send expanded prompt
    Daemon-->>UI: stream result
  • Use diff when the point is what changes and the surrounding shape already exists. Match the diff shape to the topic: component, file layout, call tree/stack, or state/control flow.
 on(save)
-  write content
+  if unchanged: return cached result
+  write content
+  invalidate cache
  • Show the whole block when most of it is new, when omitted context would hide ownership or order, or when the user needs a copyable target shape:
function expandSkill(command: string): string {
  return `use the ${command.slice(1)} skill`;
}

Guidance

Place each visual next to the short text it supports. Keep only the calls, files, props, states, and boundaries needed to answer the user's current question or the options to resolve the current discussion point.

You may use one of these, you may use several, it is unlikely you will use all of them. Use your judgement and don't overwhelm the user.

Evidence

Concrete evidence that the change works. Show a before and after.

Screenshots are S-tier - when the environment is set up for it and the change is visual.

Store screenshots on an orphan branch named pr-assets/<topic>, keeping them out of the default branch's history. Link each image by its full commit SHA. Follow the installed github-repository-configuration rules' Pull request asset branches section for permanent retention during branch cleanup.

Execution-based evidence is A-tier. Test results, console output. Show the exact test that now fails and passes, using pseudocode.

List every check you ran on the final commit with its outcome, and say why any required check was not run.

Merge Danger

Describe whether it's a one-way or two-way door. You can walk back through two-way doors, but not one-way doors. A PR that is cheap to roll back is lower risk. Changes that involve destructive actions or hard-to-reverse decisions are one-way doors.

The blast radius is the potential impact or scope of the changes introduced by this PR. Consider all possibilities. Examples are layout shift, breakages for consumers, mobile responsiveness, etc.

Name the change's relevant limits here: what it leaves undone, unverified, or unsupported. For a breaking change, explain its impact and migration in a subsection.

Related issue

Link the issue the change works on. Use a closing reference, such as Closes #123, when the PR finishes the issue, and a nonclosing one, such as Part of #123, when it does only part. For work without an issue, write Direct change: followed by the reason instead.

Reads

Paths are relative to the repository root.

  • GLOSSARY.md: the user's domain language. When it is missing, use the words the code and its issues use.
  • .repo-standards/rules/github-repository-configuration.md: permanent asset-branch retention. When it is missing, preserve the asset branch so the pull request's images remain available.

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.