LogExpert
Copilot instructions1.2k starsChanged 25 days agoLicence not identifiedView on GitHub
Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: - State your assumptions explicitly. If uncertain, ask. - If multiple interpretations exist, present them - don't pick silently. - If…
We split this copilot-instructions.md into the rules it gives an agent
35 rules. About 1 is common, 26 are distinctive, and 8 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈26
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
Trending
Quiet since August.thin dataabout the whole repository
Who's talking about LogExperts/LogExpert
- Topurrra/voli-registry“bump: auto-update 2026-08-03”GitHub · Aug 3, 2026
- Topurrra/voli-registry“bump: auto-update 2026-08-02”GitHub · Aug 2, 2026
- 6uhrmittag/PersonalKnowledgeBase“Link Checker Report”GitHub · Nov 6, 2025
- 6uhrmittag/PersonalKnowledgeBase“Link Checker Report”GitHub · Nov 5, 2025
- 6uhrmittag/PersonalKnowledgeBase“Link Checker Report”GitHub · Nov 4, 2025
The biggest 5 of 9 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 9
Talked about on GitHub (9 times).
On GitHub · 9
- Aug 3, 2026bump: auto-update 2026-08-03 — Topurrra/voli-registry0 reactions
- Aug 2, 2026bump: auto-update 2026-08-02 — Topurrra/voli-registry0 reactions
- Nov 6, 2025Link Checker Report — 6uhrmittag/PersonalKnowledgeBase0 reactions
- Nov 5, 2025Link Checker Report — 6uhrmittag/PersonalKnowledgeBase0 reactions
- Nov 4, 2025Link Checker Report — 6uhrmittag/PersonalKnowledgeBase0 reactions
4 more on GitHub
- Nov 3, 2025Link Checker Report — 6uhrmittag/PersonalKnowledgeBase0 reactions
- Nov 2, 2025Link Checker Report — 6uhrmittag/PersonalKnowledgeBase0 reactions
- Nov 1, 2025Link Checker Report — 6uhrmittag/PersonalKnowledgeBase0 reactions
- Aug 28, 2025[Update Request]: LogExpert v.1.20.0 — microsoft/winget-pkgs0 reactions · 1 comment
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.
- .github/CLAUDE.mdCLAUDE.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.

