agentleFS
oxc-projectoxc-project/oxc/.agents/skills/pr-writer/SKILL.md

pr-writer

Skill23k starsChanged 2 days agoMITView on GitHub

Write a scoped Conventional Commit title and minimal PR body for an automated Oxc triage fix.

9 other projects use a version of this.

Trending

Less talk lately.about the whole repository

Dec 2025: 3 mentionsJan 2026: 5 mentionsFeb 2026: 3 mentionsMar 2026: 4 mentionsApr 2026: 0 mentionsMay 2026: 6 mentionsJun 2026: 7 mentionsJul 2026: 5 mentionsAug 2026: 2 mentionsSep 2026: 0 mentionsOct 2026: 3 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the oxc-project/oxc repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about oxc-project/oxc

The biggest 5 of 82 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 82

Talked about on GitHub, Bluesky, YouTube, Hacker News and the web (82 times).

On GitHub · 39

34 more on GitHub

On Bluesky · 36

31 more on Bluesky

On YouTube · 5

On Hacker News · 1

On the web · 1

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the fix diff and triage/gh-<issue number>/report.md.

    line 8
  2. Very specific:

    Use a concise, scoped Conventional Commit title, such as fix(parser): handle trailing comma, following .github/workflows/pr.yml.

    line 12
  3. Very specific:

    Keep the body to a brief explanation of the user-visible problem and why the change fixes it.

    line 15
  4. Distinctive:

    Do not add headings or sections such as Tests or Evidence.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 9 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

Write an Oxc fix pull request

Read the fix diff and triage/gh-<issue number>/report.md. Return only title and body through the active finish schema; do not create or modify a pull request.

Use a concise, scoped Conventional Commit title, such as fix(parser): handle trailing comma, following .github/workflows/pr.yml.

Keep the body to a brief explanation of the user-visible problem and why the change fixes it. Include Closes #<issue number> and disclose AI assistance with Automated triagebot fix (AI-assisted).

Do not add headings or sections such as Tests or Evidence. Keep detailed validation in the triage report. Never invent test results, performance numbers, reporter confirmation, or reference behavior.

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.