agentleFS
Sign inStart free
web-infra-devweb-infra-dev/rslib/.github/copilot-instructions.md

rslib

Copilot instructions1k starsChanged 19 days agoMITView on GitHub

Use these instructions for pull request review in this repository. Focus on recurring, reusable review logic that prevents regressions. Apply these rules when reviewing Markdown, MDX, comments, examples, and user-facing guides.

We split this copilot-instructions.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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 these instructions for pull request review in this repository.

    line 5
  2. Distinctive:

    Write short, imperative feedback.

    line 10
  3. Distinctive:

    Keep suggestions aligned with the stated user goal.

    line 16
  4. Distinctive:

    Prefer fixes with limited blast radius over broad changes that can affect unrelated behavior.

    line 18
  5. Very specific:

    Use standardized command components such as <PackageManager> instead of hardcoded npm/pnpm/yarn command variants.

    line 24
  6. Distinctive:

    Call out global side effects of configuration choices and propose safer scoped alternatives when relevant.

    line 26
  7. Distinctive:

    Avoid misleading examples or outputs.

    line 27
  8. Distinctive:

    Remove duplicated explanations and keep one authoritative location per concept.

    line 28
  9. Distinctive:

    Prefer concise, copy-pasteable command examples when multiple dependencies or setup steps are required.

    line 29
  10. Distinctive:

    Ensure every mentioned package, plugin, or tool has a direct authoritative reference link.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
copilot-instructions.md

Copilot code review instructions

Purpose

Use these instructions for pull request review in this repository. Focus on recurring, reusable review logic that prevents regressions.

Instruction style

  • Write short, imperative feedback.
  • Explain the underlying rule, not a one-off line edit.
  • Suggest an actionable fix when you flag an issue.

General review rules

  • Keep suggestions aligned with the stated user goal; do not optimize for a different objective.
  • Require rationale for non-obvious design or behavior decisions.
  • Prefer fixes with limited blast radius over broad changes that can affect unrelated behavior.

Documentation review rules

Apply these rules when reviewing Markdown, MDX, comments, examples, and user-facing guides.

  • Use standardized command components such as <PackageManager> instead of hardcoded npm/pnpm/yarn command variants.
  • Link each mentioned config option or API to its canonical official documentation.
  • Call out global side effects of configuration choices and propose safer scoped alternatives when relevant.
  • Avoid misleading examples or outputs; add clarifying context when artifacts may look incorrect.
  • Remove duplicated explanations and keep one authoritative location per concept.
  • Prefer concise, copy-pasteable command examples when multiple dependencies or setup steps are required.
  • Ensure every mentioned package, plugin, or tool has a direct authoritative reference link.

Download now (ZIP)

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 2 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 8 mentionsAug 2026: 9 mentionsSep 2026: 8 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the web-infra-dev/rslib repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about web-infra-dev/rslib

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

See all 41

Talked about on GitHub and Bluesky (41 times).

On GitHub · 39

34 more on GitHub

On Bluesky · 2

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 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.

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