lumin-repo-lens

Lumin Repo Lens

🇰🇷 한국어로 읽으시려면 → README.ko.md  ·  🇬🇧 English continues below.

The kind little buddy that says "this already exists" before you write it again. Your repo's companion for vibe-coding sessions.

Sound familiar? 😅

You ask AI:

"Make me a card-news service"

AI happily spins up a new file → lib/cardNewsService.js ✨ But your repo already had three similar files in lib/cardNews/. 😱

With lumin-repo-lens riding along, Claude can say first:

🛑 "Wait — there are already 3 similar files under lib/cardNews*. Want to look before making a new one?"

Real evidence from your actual repo, not guesses.

First useful run

1. Add the marketplace and install the plugin in Claude Code

/plugin marketplace add annyeong844/lumin-repo-lens
/plugin install lumin-repo-lens@annyeong844-marketplace
/reload-plugins

2. Run the full first checkup

/lumin-repo-lens:full

→ This turns on the parts that make Lumin more than a dead-export sorter: shape index, function-clone cues, call graph, barrel discipline, topology, public-surface policies, and the grounded review profile.

3. Use the write gate when you are about to change code

/lumin-repo-lens:pre-write
# code the change
/lumin-repo-lens:post-write

Claude Code infers the compact intent internally. You do not need to write the intent JSON by hand.

💡 First run installs parser dependencies once (~30 seconds). After that, fast. For tiny follow-up checks after a fresh baseline, /lumin-repo-lens uses the quick path.

For very large repos, do not auto-trigger full profile on every edit. Run :full once per branch, first checkup, or major refactor review, then use pre-write/post-write and quick follow-ups during the agent loop.

Who is this for?

✅ Great fit if you

• code alongside AI and your repo is getting messy
• watch AI rewrite functions that already exist
• want to verify what changed after a refactor
• work in TypeScript / JavaScript, including monorepos

❌ Not a fit (yet) if you

• mainly write Python / Rust / etc. (Go is partially supported)
• don't use AI coding tools (this exists to give your AI evidence)
• have a 1–2 file mini project (the audit value won't show up)

Core commands

Maintainers can also use /lumin-repo-lens:canon-draft and /lumin-repo-lens:check-canon for canon lifecycle work.

First pass, stale or missing artifacts, explicit review, due diligence, large refactor planning, and post-refactor review should run --profile full. Small follow-up checks over a fresh baseline can use the quick path.

git clone https://github.com/annyeong844/lumin-repo-lens.git
cd lumin-repo-lens
node skills/lumin-repo-lens/scripts/audit-repo.mjs --root <repo>

LUMIN_REPO_LENS_NO_AUTO_INSTALL=1 node skills/lumin-repo-lens/scripts/audit-repo.mjs --root <repo>

git clone https://github.com/annyeong844/lumin-repo-lens.git ~/.codex/lumin-repo-lens

mkdir -p ~/.codex/skills
ln -sfn ~/.codex/lumin-repo-lens/skills/lumin-repo-lens-codex ~/.codex/skills/lumin-repo-lens-codex
ln -sfn ~/.codex/lumin-repo-lens/skills/lumin-repo-lens ~/.codex/skills/lumin-repo-lens
ln -sfn ~/.codex/lumin-repo-lens/skills/lumin-repo-lens-write-gate ~/.codex/skills/lumin-repo-lens-write-gate
ln -sfn ~/.codex/lumin-repo-lens/skills/lumin-repo-lens-canon ~/.codex/skills/lumin-repo-lens-canon