review-lep
Skill9.1k starsChanged 10 days agoMITView on GitHub
Review a Lore Enhancement Proposal for structural completeness, citation discipline, and rationale quality. Reports findings categorized by severity. Read-only.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about EpicGames/lore
- @bearstech.com“Lore : Epic Games publie un système de gestion de versions Open Source conçu pour gérer des projets à très …”Bluesky · Jun 18, 2026 · 16 likes
- @snutt.bsky.social“Epic just announced their own open source version control system 👀 github.com/EpicGames/lore”Bluesky · Jun 17, 2026 · 12 likes
- @binarynonsense.com“Interesting repository: "Lore - a next-generation, open source revision control system (EpicGames)" …”Bluesky · Jun 18, 2026 · 10 likes
- A Hacker News story“Lore: Next-generation open source version control”Hacker News · Jun 27, 2026 · 4 points
- @zooko2.bsky.social“Lore: new revision control system built by EpicGames with BLAKE3+FastCDC+Zstd github.com/EpicGames/lore”Bluesky · Jun 21, 2026 · 4 likes
The biggest 5 of 39 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 39
Talked about on GitHub, Bluesky and Hacker News (39 times).
On GitHub · 26
- Jun 22, 2026registry: add lore — jdx/mise1 reaction · 2 comments
- Nov 10, 2026build(deps): bump lore from v0.12.0 to v0.13.0 — carapace-sh/scrape0 reactions
- Nov 8, 2026epic-lore: update to 0.13.0 — macports/macports-ports0 reactions
- Nov 2, 2026build(deps): bump lore from v0.11.0 to v0.12.0 — carapace-sh/scrape0 reactions
- Oct 27, 2026Support for Lore VCS — ros-infrastructure/vcs2l0 reactions · 1 comment
21 more on GitHub
- Oct 27, 2026build(deps): bump lore from v0.10.1 to v0.11.0 — carapace-sh/scrape0 reactions
- Oct 12, 2026build(deps): bump lore from v0.10.0 to v0.10.1 — carapace-sh/scrape0 reactions
- Oct 7, 2026build(deps): bump lore from v0.10.1 to v0.10.0 — carapace-sh/scrape0 reactions
- Oct 6, 2026build(deps): bump lore from v0.10.0 to v0.10.1 — carapace-sh/scrape0 reactions
- Sep 22, 2026build(deps): bump lore from v0.9.0 to v0.10.0 — carapace-sh/scrape0 reactions
- Sep 4, 2026build(deps): bump lore from v0.8.6 to v0.9.0 — carapace-sh/scrape0 reactions
- Aug 9, 2026Strip debug info from Linux `liblore.so` in `build_lore_crate.cmake` — theRTC204/godot-lore-plugin0 reactions
- Jul 31, 2026SBAI-5906: parity watcher reports true pinned distance, not last-hop delta — BiloxiStudios/loregui0 reactions · 4 comments
- Jul 16, 2026Update repo table — arran4/arran40 reactions
- Jul 4, 2026Add support for lore — timonkrebs/Time-Tracer0 reactions
- Jul 3, 2026Vendoring "lore": failed to get `bitcode` as a dependency of package ... — openSUSE-Rust/obs-service-cargo0 reactions · 7 comments
- Jul 1, 2026Update repo table — arran4/arran40 reactions
- Jun 30, 2026Update repo table — arran4/arran40 reactions
- Jun 29, 2026Update repo table — arran4/arran40 reactions
- Jun 28, 2026Add Lore icon — simple-icons/simple-icons0 reactions
- Jun 27, 2026[FEAT] INVESTIGATE - Lore VCS — LAF-US/IDAHO-VAULT0 reactions
- Jun 18, 2026每日速递 Daily Digest — 2026-06-18 — Aurora-yang-git/DailyNews-Bilingual_AI_Digest0 reactions
- Jun 18, 2026Support a Lore VCS backend in git-diff (blocked on Lore stabilization) — itsakeyfut/uasset-lens0 reactions · 1 comment
- Jun 17, 2026[Request]: loreserver — ScoopInstaller/Main0 reactions
- Jun 17, 2026[Request]: lore — ScoopInstaller/Main0 reactions
- May 28, 2026Link checker report — tldr-pages/tldr-maintenance0 reactions
On Bluesky · 12
- Jun 18, 2026Lore : Epic Games publie un système de gestion de versions Open Source conçu pour gérer des projets à très grande échelle mêlant code et… — @bearstech.com16 likes and reposts · 2 replies
- Jun 17, 2026Epic just announced their own open source version control system 👀 github.com/EpicGames/lore — @snutt.bsky.social12 likes and reposts · 2 replies
- Jun 18, 2026Interesting repository: "Lore - a next-generation, open source revision control system (EpicGames)" github.com/EpicGames/lore #gamedev… — @binarynonsense.com10 likes and reposts
- Jun 21, 2026Lore: new revision control system built by EpicGames with BLAKE3+FastCDC+Zstd github.com/EpicGames/lore — @zooko2.bsky.social4 likes and reposts
- Jun 17, 2026Epic released a new open source control version software called Lore, it’s designed with large repos and handling large binary files in… — @djlink.bsky.social3 likes and reposts · 3 replies
7 more on Bluesky
- Jul 12, 2026Seriously though Lore is really interesting for a bunch of reasons, like treating binary data as a first class citizen rather than being… — @skinchanger.dev2 likes and reposts
- Jul 3, 2026you're not gonna believe this github.com/EpicGames/lore — @spamcan.bsky.social1 likes and repost · 1 reply
- Jun 28, 2026Epic Games open-sourcing a VCS built specifically for binary-heavy game projects fills a real gap that Git LFS only partially addresses —… — @u11g.com1 likes and repost
- Jun 27, 2026Just came across Epic Games' Lore, their new version control. A promising solution for projects that mix code with large binary files like… — @luise.ac1 likes and repost
- Jun 20, 2026One of the pains in the gaming industry -and possibly the greater entertainment one- is dealing w/ large files amidst version control… — @diegum.bsky.social1 likes and repost · 1 reply
- Jun 18, 2026EpicGames/lore: Lore is a next-generation, open source revision control system #devopsish github.com/EpicGames... — @chrisshort.net1 likes and repost
- Jun 22, 20267. Epic Games released Lore, an open-source VCS written in Rust that tackles code and hefty binary assets alike. Think version control, but… — @rustaceans.bsky.social0 likes and reposts · 1 reply
On Hacker News · 1
- Jun 27, 2026Lore: Next-generation open source version control4 points
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lore-developmentSkill
- review-changeSkill
- smoke-testsSkill
- write-lepSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
If a path was provided as an argument, use it.
- Distinctive: line 28
If the path doesn't exist, report the error and stop.
- Distinctive: line 32
Use the Read tool to read:
- Distinctive: line 39
If the LEP already has review comments, read them.
- Very specific: line 49
All required fields present: lep, title, authors, status, created, updated, discussion.
- Very specific: line 53
If replaces is set, the referenced LEP exists in docs/proposals/.
- Very specific: line 75
No section contains {TODO}, {...} placeholders, or other template scaffolding left from lep-template.md.
- Very specific: line 81
If status: Accepted, the Unresolved Questions section is empty or contains only public references to follow-up work.
- Distinctive: line 170
Do not edit the LEP. Reviewing is read-only.
- Distinctive: line 176
Do not require citations for claims the LEP itself is the source for — the author proposing a new design does not need to cite themselves.
- Very specific: line 177
Do not run the review on docs/proposals/lep-template.md or docs/proposals/README.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
Review LEP
Review a Lore Enhancement Proposal in docs/proposals/ and report findings categorized by severity. The skill is read-only — it does not edit the LEP. The author is responsible for applying any fixes.
The review has three phases:
- Structural — deterministic check that all required sections and frontmatter fields are present and filled.
- Citations on claims — every factual claim must reference a public source (ADR, code path in the Lore tree, benchmark, upstream doc) or carry its support inline.
- Rationale quality — alternatives, drawbacks, and risks must be load-bearing rather than checkbox-filling.
Arguments
- No arguments: The skill will list all
docs/proposals/*.mdfiles (excludingREADME.mdandlep-template.md) and ask which to review. <path>: Path to the LEP to review, e.g./review-lep docs/proposals/2026-04-27-fragment-flag-reorganization.md.
Instructions
Step 1: Locate the LEP
If a path was provided as an argument, use it. Otherwise list docs/proposals/*.md (excluding README.md and lep-template.md) and ask the user which to review.
If the path doesn't exist, report the error and stop.
Step 2: Read the LEP, the README, and the template
Use the Read tool to read:
- The LEP under review.
docs/proposals/README.md— per-section rules and cross-cutting rules (active voice, public citations, no fabrication).docs/proposals/lep-template.md— section structure and frontmatter shape.docs/glossary.md— the Lore terms the proposal must use in their defined sense.
If the LEP already has review comments, read them. Treat them as input to verify, and refer to a point a comment already makes rather than repeating it.
Phase 3 references rules from docs/proposals/README.md rather than restating them.
Step 3: Phase 1 — Structural check
Deterministic. For each item, mark PASS or FAIL. Note the line number where applicable.
Frontmatter:
- All required fields present:
lep,title,authors,status,created,updated,discussion. statusis one ofDraft,Accepted,Rejected.lepvalue matches the filename (without.md).createdandupdatedare validYYYY-MM-DDdates.- If
replacesis set, the referenced LEP exists indocs/proposals/. - If
superseded-byis set, the referenced LEP exists indocs/proposals/.
Body sections (all 14 must be present in order):
- Summary
- Motivation
- Goals / Non-Goals
- Proposed Design
- Compatibility (with four items: Wire format, Client/server protocols, On-disk format, CLI and public API)
- Non-Functional Considerations
- Migration Plan
- Security Considerations
- Privacy Considerations
- Risks and Assumptions
- Drawbacks
- Alternatives Considered
- Prior Art (may be omitted with explicit justification)
- Unresolved Questions
Content checks:
- No section contains
{TODO},{...}placeholders, or other template scaffolding left fromlep-template.md. - Each Compatibility item (Wire format, Client/server protocols, On-disk format, CLI and public API) is filled or marked
N/A. A reason after the dash is helpful but not required structurally. WhetherN/Ais correct given the rest of the proposal is checked in Phase 3. - Migration Plan is filled or marked
N/A. Phase 3 verifies consistency with Compatibility. - Security Considerations is filled.
N/Ais not acceptable here — if there are no security implications, the section must say so explicitly and explain why. - Privacy Considerations is filled.
N/Ais not acceptable here — if there are no privacy implications, the section must say so explicitly and explain why. - Non-Functional Considerations is filled. The section addresses concurrency, memory, statelessness, and determinism — either confirming the proposal preserves each property or naming the impact and how the design accommodates it. Whether the response for each property is correct given the rest of the proposal is checked in Phase 3.
- If
status: Accepted, the Unresolved Questions section is empty or contains only public references to follow-up work. Open questions in an Accepted LEP are a FAIL.
Step 4: Phase 2 — Support for claims
LEPs are publicly consumable. Every factual claim must be supported in a way an external reader can verify or evaluate. There are two acceptable forms of support:
- A public citation — a link to a public document, RFC, code path in the Lore tree, ADR, internals doc, or upstream project doc. The reader can follow the link.
- Inline detail — the relevant data, code reference, paraphrased constraint, or excerpt captured in the LEP body. The reader sees the support without leaving the document.
Internal-only links do NOT count as support. Internal code reviews, JIRA tickets, Slack threads, internal wikis, and any other resource gated behind the company SSO are not visible to external readers. If a claim's only support is an internal link, flag it and require the author to either replace the link with a public citation or capture the relevant detail inline.
Categories of claim that require support:
- Quantitative claims — numbers, percentages, throughputs, sizes, latencies (e.g. "reduces storage by 40%", "compresses at 136 MiB/s"). Acceptable: benchmark table inline, link to a public benchmark or ADR with the data.
- Claims about current Lore behavior — how Lore works today (e.g. "fragment flags occupy bits 0-9", "the mutable store uses RocksDB"). Acceptable: link to the relevant code path or doc in the Lore tree, paraphrase of the behavior with file/function reference.
- Claims about other systems — Git, Mercurial, Perforce, Jujutsu, etc. (e.g. "Git's hash transition uses translation tables"). Acceptable: link to the upstream doc, paraphrase with concrete enough detail to reconstruct the claim.
- Claims about decisions or constraints — prior decisions or external requirements (e.g. "approach X was ruled out due to Y", "compliance requires per-tenant encryption"). Acceptable: paraphrased rationale captured inline, link to a public ADR or LEP.
Categories of claim that do NOT require support:
- The author's own design proposals — the LEP is the primary source for what it proposes.
- Genuinely common knowledge — "SHA-256 produces a 32-byte digest", "TCP is a stream protocol".
- Claims explicitly framed as assumptions in the Risks and Assumptions section — those need an invalidation condition, not a citation.
For each unsupported claim, record: section name, line number, the claim text, and whether the author needs a public citation or inline detail. For each claim supported only by an internal-only link, record the same plus the offending link.
Step 5: Phase 3 — Rationale quality
LLM judgment. Each bullet names a rule and points to where it is defined; verify the LEP against that rule. docs/proposals/README.md is the source of truth — do not restate or substitute. Flag violations with section name, line number, and a one-line description of what to strengthen.
- One decision per proposal — see README cross-cutting rules. Flag a proposal whose parts have their own goals, risks, and compatibility surface, so that accepting one decides the others. Name the split, the order the parts depend on each other, and any part that belongs in an amendment to an accepted LEP (README
Lifecycle). Required fix. - Design level — see README
Proposed Design. Walk Proposed Design, and flag implementation detail: names of functions, types, and files that aren't a compatibility surface, constants that aren't a stated limit or fixed by a format Compatibility names, struct ownership, and the order of steps inside a command. For each, say what moves to the spec and what property stays. Required fix when implementation detail makes up most of Proposed Design; recommended otherwise. - Lore terms — see README cross-cutting rules. Flag a term the glossary defines that the proposal uses in another sense, and a Git or Perforce term
docs/developing/doc-standards/canon/language.mdmaps to a Lore term. - Goal → Design coverage — see README
Proposed Design. - Motivation → Design coverage — see README
Proposed Design. Also flag design content that traces to neither a Motivation problem nor a Goal (over-scoped). - Motivation describes the problem, not the solution — see README
Motivation. Flag passages that prescribe how ("we require pagination", "we need read/write separation") instead of naming the user need or constraint ("lists can be very large and need navigation", "background operations must not block foreground requests"). Recommended fix. - Compatibility — N/A consistency — for each sub-section marked
N/A, walk Proposed Design, Migration Plan, Risks and Assumptions, and Drawbacks. If any concern there touches that surface, theN/Ais contradicted — required fix. (BareN/Awithout a reason is fine on its own; the test is whether the proposal's other content disagrees.) - Compatibility — surfaces beyond the four standard items — see README
Compatibility("Add additional items for any other compatibility surface…"). If the proposal touches a surface (configuration formats, env vars, third-party library APIs, plugin interfaces, file paths treated as stable, etc.) and Compatibility omits it as a custom item, flag the gap. - Compatibility — concreteness — for each non-
N/Asub-section, verify the answer addresses the questions in the README (specific bits, specific commands, specific protocol fields). Hand-wavy answers ("there will be some impact") are recommended fixes. - Non-Functional — N/A consistency — for each property dismissed as
N/Aor "preserved", walk Proposed Design, Risks and Assumptions, and Drawbacks. If any concern there touches that property, the dismissal is contradicted — required fix. - Non-Functional — concerns beyond the four standard items — see README
Non-Functional Considerations. Same logic as Compatibility's additional-surfaces check, with non-functional concerns such as latency, throughput, durability, ordering guarantees, backpressure, error budgets, observability. - Migration Plan — see README
Migration Plan. If any Compatibility sub-section flags a breaking change but Migration Plan isN/A, theN/Ais contradicted — required fix. Otherwise verify named transition phases with read/write compatibility matrices, plus rollback signal and recoverable state. Hand-wavy phases or missing rollback are recommended fixes. - Risks and Assumptions structure — see README
Risks and Assumptions. Each Assumption must carry an*invalidated if:*clause; each Risk must carry a*mitigation:*clause. Mixed bullets without the two-list structure are recommended fixes. - Risks and Assumptions — load-bearing — generic risks ("could have unexpected interactions", "performance might be worse") add no value.
- Drawbacks shape — see README
Drawbacks. One sentence each; not re-statable as an Assumption (premise that could be wrong) or a Risk (failure mode); not generic hedges ("more code to maintain", "may require documentation updates"). - Alternatives Considered — see README
Alternatives Considered. ≥2 alternatives, each with a concrete rejection reason. Strawmen and lazy rejections ("this would be harder") are recommended fixes; the status quo is a valid alternative if the rejection reason is concrete. - Goals / Non-Goals — toothless Non-Goals — Non-Goals must narrow scope. Obvious things nobody would expect ("we're not solving world hunger") are recommended fixes.
- Active voice — see README cross-cutting rules. Flag true passive constructions and suggest active rewrites; past-participle adjectives are fine.
For each weakness, record: section name, line number where applicable, and a one-line description of what to strengthen.
Step 6: Report
Output a structured report with three buckets:
Required fixes — must be addressed before the LEP can move to Accepted:
- Any structural FAIL.
- Any uncited quantitative claim.
- Empty Security Considerations.
- Open Unresolved Questions when
status: Accepted. - Any
N/Ain Compatibility, Non-Functional Considerations, or Migration Plan, and any property marked preserved, that the rest of the proposal contradicts. - Independent decisions bundled in one proposal.
- A Proposed Design given mostly to implementation detail.
Recommended — should be addressed but not blocking:
- Uncited claims about Lore behavior or other systems.
- A Goal or Motivation problem the design doesn't address, and design content that traces to neither.
- A compatibility surface or non-functional concern the proposal touches but doesn't list.
- Implementation detail in an otherwise design-level section.
- Terms used in a sense other than the glossary's.
- Toothless Non-Goals.
- Hand-wavy Compatibility or Migration Plan.
- Generic Drawbacks or Risks.
- Weak Alternatives Considered.
Optional — nice-to-haves:
- Style, polish, formatting, and passive constructions.
- Suggestions for stronger Prior Art coverage.
- Cross-references to related LEPs or ADRs that could be linked.
For each item: section name, line number where possible, and a one-line description.
End the report with a one-line summary: "Required: N. Recommended: N. Optional: N." If Required is 0, state that the LEP passes structural and citation review.
Step 7: Stop
Do not edit the LEP. Reviewing is read-only; the author makes the changes.
Notes
- Be specific. "Section X has a problem" without a line number or quote is not actionable. Always cite the line and quote enough text for the author to find the issue.
- Be charitable in Phase 3. Push back on weak rationale, but recognize that judgment calls are not always black-and-white. If you're unsure whether something is a generic hedge or a real drawback, classify it as Optional with a note.
- Do not require citations for claims the LEP itself is the source for — the author proposing a new design does not need to cite themselves.
- Do not run the review on
docs/proposals/lep-template.mdordocs/proposals/README.md. If the user points at one of those, decline and explain why.
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.

