You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository uses Kin semantic VCS. Kin indexes every function, class,
type, and trait into a graph with cross-file relations. Use Kin tools
instead of raw file operations whenever possible.
Finding Code (use Kin instead of grep/rg/find)
Instead of
Use
Why
grep -r function_name
kin search function_name
Returns exact entity definitions with file:line, not noisy text matches
rg 'class Foo'
kin search Foo --kind class
Disambiguates: shows only definitions, not usages
find . -name '*.rs' then read each
kin search --language rust
Queries the semantic graph, no filesystem walk
Reading Code (use Kin instead of cat/read entire files)
kin search <pattern># Find entities (functions, classes, types)
kin search <p> --kind <k># Filter by kind: function, class, struct, trait
kin search <p> --language <l># Filter by language: rust, typescript, python, go, java
kin context <entity># Token-budgeted context pack
kin support # Coverage report (entities, languages, relations)
kin review # Semantic diff + impact + risk assessment
kin commit -m "msg"# Semantic commit
kin history# Entity change history
kin work list # Outstanding work items
kin verify <entity># Check test coverage for an entity
Key Principle
Search semantically first, read files second. Kin search returns 4-22x
less noise than grep and context packs use 84% fewer tokens than reading
all matching files. Only fall back to raw file reads when Kin doesn't have
what you need.
Conventions
Use kin commit -m "message" for semantic commits
Use kin context <entity> for token-budgeted context packs
Use kin review for semantic impact analysis before merging
Use kin search <pattern> to find entities across the codebase
Verification
Work items: 0
Use kin verify <entity> to check test coverage for an entity