Byori — Development skill for Claude Code

**English** | [한국어](docs/ko/README.md)

Byori

**The memory of your software project.**

Git remembers what changed. Byori remembers why.

Every coding agent forgets. Your project shouldn't.

$ byori init                       # reads the repository's own history
analyzed
  11,814 commits · 1,858 tracked files · 1,042 pull requests
discovered
  module 24 · bug 72 · task 64 · decision 19 · relations 453

$ ask any agent: "why was sendfile removed from replication?"

without Byori   "I can only see the current implementation. There is no
                 sendfile code here, so I cannot say whether it ever existed."

with Byori      bug:redis-revert-61074b43   (evidence-backed)
                Reverted on 2020-06-06: "Implements sendfile for redis."
                  (commit 9cf500a3f67e)
                A revert is the history stating the change was wrong; why it
                was wrong is not in the commit, so it is not recorded here.

**On redis's full history: 8/8 questions answered with the graph, 0/8 without it**, where a pass means the answer cited a commit or pull request a reader can open. Ingest took 11 seconds. Reproduce it: [`benchmarks/why.py`](benchmarks/why.py).

Byori preserves that chain rather than a pile of summaries:

incident ──caused_by──> bug ──fixed_by──> decision ──affects──> module
                                      └──supersedes──> previous decision

Vector search recalls a similar paragraph; this recalls the reason — and says what it is standing on. Every memory is labelled `evidence-backed` or `unsourced`, and a decision that something newer replaced comes back marked `stale`, because a memory nobody can check is worth less than one that cites a commit, and last year's decision presented as current is worse than no answer.

What it is made of

byori init	Builds the sta