review-change
Skill9.1k starsChanged 10 days agoMITView on GitHub
Must be used before submitting any change to Lore, and to review another author's change. Reviews the change adversarially, in a fresh session, against code-review.md and the standards it names. On your own branch it fixes the findings that have one obvious fix and reports the rest; on another author's change it reports the findings by severity.
29 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- Krzysztof318/MailFathomtheir own version, first seen Nov 15, 2026
- CsHeng/agent-skillstheir own version, first seen Nov 9, 2026
- SaKaNa-Y/skillstheir own version, first seen Nov 8, 2026
- 0xdeafcafe/skillstheir own version, first seen Nov 6, 2026
- Esri/calcite-design-systemtheir own version, first seen Nov 2, 2026
- marinvch/Cortextheir own version, first seen Nov 1, 2026
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
Used with
Projects with it also use plan-change, implement-change and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BanKnightSkillplan-change
将已完成 spec/design 的 change 拆成可执行 plan 与 tasks。用户要把设计落成执行计划、任务清单或实现步骤时使用。
Also in 7 projects that use this
Codagent-AISkillimplement-change
Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.
Also in 7 projects that use this
MaheshAwasareSkillwrite-runbook
Generate an operational runbook for a service from its code, config, and dependencies — what to do when it breaks, where to look, how to roll back, who to escalate to. Use proactively before a service goes to production, after a major incident, or when handing off operational ownership.
Also in 3 projects that use this
testified-ossSkillincident-triage
Triage production incidents with severity assessment, root cause hypothesis, impact analysis, and escalation recommendations. Use when analyzing outages, errors, or production issues.
Also in 4 projects that use this
srclightSkillrefactor-safely
This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.
Also in 3 projects that use this
Google CloudSkillopen-pr
Commits local changes to a new Git branch and opens a GitHub pull request through the configured GitHub MCP server. Use when proposing code changes in a new pull request. Don't use for local-only commits without a remote GitHub repository.
Also in 4 projects that use this
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- ben-manes/caffeine★ 18ksame name
- maypok86/otter★ 2.7ksame name
- aquaproj/aqua-registry★ 398same name
- Esri/calcite-design-system★ 385same name
- yiming-liao/intor★ 211same name
- gtrabanco/agentic-workflow★ 23same name
- fathomise/MailFathom★ 21same name
- Krzysztof318/MailFathom★ 21same name
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
19 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lore-developmentSkill
- review-lepSkill
- smoke-testsSkill
- write-lepSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
2
Distinctive
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
- Very specific: line 35
Read code-review.md and every standard its Guidance names, in full and in its own session.
- Distinctive: line 36
Read each changed function and type in full with its doc comments, each changed doc page in full, and the code the change calls and is …
- Distinctive: line 45
Check each finding against the code yourself.
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review change
Review a change to Lore as docs/developing/code-standards/code-review.md describes. The rules live in that file and in the standards its Guidance names. This skill is the procedure for applying them, and restates only what a step needs.
Arguments
- No arguments: review the current branch against its parent branch.
<branch>: review that branch, another author's change.
Findings from an earlier review, and comments already on the review, are input to verify, not conclusions.
Step 1: Establish the change
Find the branch, its base, and the change's description. For your own branch, lore branch info names the parent branch, lore branch diff <parent> lists the committed changes, and lore status lists the changes not yet committed. Review both.
Check out another author's branch in an instance of its own over the shared store, with lore clone <remote-url> <path> --branch <branch> --use-shared-store. Don't switch your own working tree to it. In that instance, lore branch diff <parent> lists the changes and names the base revision they're computed from. Compare files against that base, checked out with lore clone <remote-url> <path> --revision <base> --use-shared-store, not against the parent's latest revision, which also holds the parent's newer changes.
In a git clone, git merge-base, git diff --name-only <base> and git status give the same lists, and git worktree add checks out another author's branch.
Record the revision you review, and whether the working tree holds changes beyond it. Every finding refers to it.
Step 2: Review in a fresh session
You must spawn a subagent to review: the context that wrote the change carries its reasoning, and a review from it confirms what the author meant rather than what the code does. Give it the instance path, the branch, its base, the revision, the change's description, and the earlier findings and comments. Don't give it the reasoning behind the change.
Tell the subagent to:
- Load the
lore-developmentskill, and skip its review step: the subagent is that review. - Read
code-review.mdand every standard its Guidance names, in full and in its own session. Ofsystem-design.mdand the ADRs, read the sections and decisions for the area the change touches. - Read each changed function and type in full with its doc comments, each changed doc page in full, and the code the change calls and is called from. Read from the code, not from memory.
- Review the change as
code-review.mddescribes. Performance and allocations come first. - Return each finding as Reporting findings in
code-review.mddescribes, and edit no file. - List the standards it read at the top of its findings.
A change that adds or edits a proposal in docs/proposals/ is also reviewed with the review-lep skill, in a second subagent given the same input, spawned beside the first. Report its findings in its own Required, Recommended and Optional buckets, after the findings by severity.
Step 3: Verify the findings
Check each finding against the code yourself. Drop a finding the code doesn't support, and say why. Don't add a finding you haven't checked.
Step 4: Match tracked work
When context/team-workspace.md exists, search the work items it describes for open and deferred items that cover each finding. Refer to a covered finding by its work item rather than fixing or filing it again. A finding a work item defers stays deferred unless the user decides otherwise. Without that file, or without access to the work items, skip this step and say so.
Step 5: Act on the findings
Your own branch
- Fix each finding that has one obvious fix. A defect's fix must start with a test that fails without it, as
testing.mddescribes in What a change tests. - Build and run the tests the fixes touch, as the
lore-developmentskill describes. - Record the state of the working tree again, and review again from step 2 in a new subagent, with the fixed findings as input. Repeat until a review reports nothing new, for at most three rounds, then report what remains.
- Report the remaining findings to the user by severity: those with several reasonable fixes, design choices and trade-offs. Give the options for each, and recommend one.
- File each finding left for later as a work item, where step 4 found work items to search.
Another author's change
- Report the findings in the conversation by severity. Don't change the author's code.
- Post the findings to the review only when the user asks. Post one comment per severity, and name the revision reviewed at the top of each.
- Refer to a point an existing comment already makes rather than repeating it.
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.

