agentleFS
jaegertracingjaegertracing/jaeger/.github/copilot-instructions.md

jaeger

Copilot instructions23k starsChanged 48 days agoApache-2.0View on GitHub

Prefer silence over uncertainty. A review comment has a cost — it demands the author's attention, may trigger another round, and can obscure the comments that actually matter. Only post a comment when you are confident the issue is real and material. Flag genuine defects in the diff: logic errors, incorrect conditions, missing error handling, concurrency hazards, resource leaks, security regressions, data corruption. These always warrant a comment. - Style and formatting — CI enforces these automatically. Do not comment…

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Prefer silence over uncertainty.

    line 5
  2. Distinctive:

    Before posting, ask: is this a correctness or security defect that a careful human reviewer would block the PR on?

    line 33

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

Core principle

Prefer silence over uncertainty. A review comment has a cost — it demands the author's attention, may trigger another round, and can obscure the comments that actually matter. Only post a comment when you are confident the issue is real and material.

What to flag

Flag genuine defects in the diff: logic errors, incorrect conditions, missing error handling, concurrency hazards, resource leaks, security regressions, data corruption. These always warrant a comment.

What not to flag

  • Style and formatting — CI enforces these automatically. Do not comment on indentation, line length, naming conventions, comment phrasing, or anything a linter or formatter would catch.
  • Pre-existing issues — if a problem exists in code the PR did not introduce, do not raise it. The PR is not the right vehicle to fix it.
  • Low-confidence observations — if you are not certain an issue is real, stay silent. Do not post speculative or "consider whether..." comments.
  • Already-raised issues — if you flagged something in an earlier review round on this PR and the author did not act on it, do not raise it again. Either it was resolved, or the author made a deliberate choice. Repeating it creates noise without value.

Threshold

Before posting, ask: is this a correctness or security defect that a careful human reviewer would block the PR on? If not, stay silent.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 3 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the jaegertracing/jaeger repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about jaegertracing/jaeger

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

See all 45

Talked about on GitHub, Stack Overflow, YouTube, the web and Hacker News (45 times).

On GitHub · 21

16 more on GitHub

On Stack Overflow · 12

7 more on Stack Overflow

On YouTube · 7

2 more on YouTube

On the web · 4

On Hacker News · 1

  • 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 repository2 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.