Skip to content

Incremental, resolving index; JS/TS, config and env keys; context, impact and an MCP server - #1

Merged
decentralizeallengineering merged 1 commit into
mainfrom
land/incremental-index
Oct 27, 2026
Merged

decentralizeallengineering merged 1 commit into
mainfrom
land/incremental-index

Conversation

@decentralizeallengineering

Copy link
Copy Markdown
Owner

Squashed from the cloud session branch claude/amazing-knuth-a3ld6v. Incremental builds by git blob hash, callers marked resolved or name-only, JS/TS plus TOML/JSON config keys and env-var reads, and new changed, dead, context, impact and mcp commands. The README tables come from bench/bench_build.py and bench/agent_chars.py, both of which were run from the fresh clone. The one changed test assertion was strengthened, not loosened. Vetted in a fresh clone on Python 3.11: scrub clean, 22 tests pass, CI green on the branch head.

…pact and an MCP server

A build now re-parses only files whose git blob hash changed. Callers are
marked resolved or name-only. JavaScript and TypeScript, TOML and JSON
config keys and environment-variable reads are indexed. New commands:
changed, dead, context, impact and mcp; the MCP server finds the repo from
CLAUDE_PROJECT_DIR when Claude Code starts it. bench/bench_build.py and
bench/agent_chars.py produce the README tables, and a skill file tells an
agent when to use each command.
@decentralizeallengineering
decentralizeallengineering merged commit cac5ba9 into main Oct 27, 2026
4 checks passed
@decentralizeallengineering
decentralizeallengineering deleted the land/incremental-index branch October 27, 2026 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant