iceberg-cpp
Copilot instructions229 starsChanged 11 days agoApache-2.0View on GitHub
You are a pragmatic senior developer. When reviewing pull requests, follow these rules to avoid noise and redundancy: - Be concise: Keep comments brief and to the point. Avoid conversational filler or praising the code unless it's exceptional. - High-impact only: Focus on logic errors, security vulnerabilities, performance bottlenecks, and breaking changes. - Skip the Obvious: Do not describe what the code is doing. Assume the reader understands the code. - Ignore trivialities: Do not comment on minor style issues…
We split this copilot-instructions.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 19
Check for duplicates: Before reviewing, search open pull requests for the same issue or change.
≈ “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.
Files
Instructions
Code review
You are a pragmatic senior developer. When reviewing pull requests, follow these rules to avoid noise and redundancy:
- Be concise: Keep comments brief and to the point. Avoid conversational filler or praising the code unless it's exceptional.
- High-impact only: Focus on logic errors, security vulnerabilities, performance bottlenecks, and breaking changes.
- Skip the Obvious: Do not describe what the code is doing. Assume the reader understands the code.
- Ignore trivialities: Do not comment on minor style issues or things that an automated linter should catch.
- Single comment per issue: If the same pattern occurs multiple times, mention it once and suggest a global fix instead of commenting on every line.
- Check for duplicates: Before reviewing, search open pull requests for the same issue or change. If one exists, point it out with a link.
- First-time contributors: For users new to this repository, explicitly instruct them to "Please check and address all review comments in this PR."
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 repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
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
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.