agentleFS
Sign inStart free
t3dotggt3dotgg/tstack/skills/file-pr/SKILL.md

file-pr

Skill2.5k starsChanged 8 days agoMITView on GitHub

File a concise pull request. Use when the user asks to file, open, or create a PR.

  • Commits and pushes

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    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
  1. Very specific:

    Before filing, check whether a PR for this branch already exists.

    line 8
  2. Distinctive:

    If model identity is unavailable, name the harness without guessing a model.

    line 39
  3. Distinctive:

    Before submission, check the title, description, quotes, and attachments for secrets and private details.

    line 41
  4. Very specific:

    Do not post a follow-up PR comment unless it serves the user's request.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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

File PR

Before filing, check whether a PR for this branch already exists. Review the diff locally against the base branch (usually origin/main) to make sure its contents match the goal.

PR titles usually become commit messages, so follow the repository's title conventions. Look at recently merged PRs and Git history for examples. Prefer a concise, human-readable title that explains why the change matters:

BAD

❌ perf(server): negotiate permessage-deflate on the websocket

GOOD

✅ perf(server): cut websocket frame size by 70%+ with gzipping

Open the description with a simple explanation of the problem based on the user's original prompt, then briefly explain the solution. Do not lead with an implementation inventory:

BAD

❌ Removed implicit workspace carry-over from every "new thread" entry point (cmd+n / cmd+shift+o, sidebar v1/v2 buttons, command palette). New threads inherit only the project from context; branch, worktree, and env mode always come from the configured defaults. Deleted buildContextualThreadOptions, startNewThreadInProjectFromContext, and the v1 sidebar's seed-context machinery.

GOOD

✅ My "new worktree" default was ignored when starting new threads on existing worktrees. Super unintuitive. Now your preferences always apply.

End the description with the public model name and harness that made the changes, for example Created with <model> in <harness>. Include subagent models that wrote part of the change. Use the model name the harness reports. If model identity is unavailable, name the harness without guessing a model.

Before submission, check the title, description, quotes, and attachments for secrets and private details.

Open a real PR rather than a draft so review bots run. If gh pr create fails because the GraphQL rate limit is used up, open it through REST with gh api repos/<owner>/<repo>/pulls -f title=... -f head=... -f base=... -F body=@<file>. If the user also asked to babysit it, continue with the babysit-pr skill.

Do not post a follow-up PR comment unless it serves the user's request. When a comment is needed, use the leaving-pr-comments skill.

Download now (ZIP)

Trending

Surging: 2 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 1 new projectWeek of Oct 18: 1 new project
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 2 in all, so this is a hint, not a trend.
  • Other versions14 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 7

    1. itsyasirkhandev/skills★ 488% same
    2. connorch/skills★ 293% same
    3. Dhruv2mars/skills★ 249% same
    4. falcondev-oss/skills★ 216% same
    5. ejarmand/skills★ 132% same
    6. lrstanley/skills★ 132% same
    7. pedrobarretto/skills★ 092% same

    Wrote their own version · 7

    1. GeiserX/agent-skills★ 4same name
    2. GeiserX/claude-skills★ 4same name
    3. bhagyamudgal/skills★ 2same name
    4. JorgeMenaDev/skills★ 1same name
    5. MichaelHolley/cc-plugins★ 0same name
    6. ShlomiPorush/agent-skills★ 0same name
    7. zzacong/agent-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use review-pr, research and 1 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • DockerSkill

      review-pr

      Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

      Also in 3 projects that use this

    • NVIDIASkill

      research

      Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

      Also in 4 projects that use this

    • Hugging FaceSkill

      implement

      Make tests pass. Invoke after /write-tests produces failing tests.

      Also in 3 projects that use this

  • In this repository8 other files it gives its agents.

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