Software engineer · Open-source builder
I build tools that help developers and coding agents understand complex codebases, make deliberate changes, and verify the outcome.
Thoughtful tools for working with code.
Levencode Labs is my open-source home for developer tooling. Four connected areas: understanding the impact of a change, planning safe dependency upgrades, checking project conventions, and migrating legacy test code with explicit evidence.
Know what a change might affect before making it.
A local-first tool for JavaScript, TypeScript, and React: trace symbols, components, routes and tests; estimate a refactor's blast radius; and find newly orphaned exports. Built for developers and coding agents through CLI, MCP, and an Agent Skill.
In development · 0.0.1-dev preview, not a published v0.1.0 release.
Dependency upgrades with an inspectable plan, not a leap of faith.
Deploom helps developers and agents reason about version choices, peer constraints, upgrade scope, and missing evidence. Planning and actual installation or runtime verification are deliberately separate.
Projects: Deploom Core · Deploom MCP · Deploom npm
Get started · Руководство · Dependency Lab
Make project-specific code review expectations explicit.
SelfReview turns conventions found in source code, team agreements, and review feedback into inspectable rule candidates. Approved rules can be checked using local AST analysis, a CLI, and an ESLint adapter; unsupported cases remain visible for review.
Repository · User guide · Руководство
From Selenium C# NUnit to Playwright .NET, with verifiable evidence.
Migrator combines a Roslyn-backed migration engine with an MCP server and Agent Skill. Analyze legacy tests, explain blockers, preview conservative Playwright candidates, and verify exact artifacts without silently applying changes.
Projects: Migrator Core · Migrator MCP
In development · Windows Chromium lifecycle investigation #59 remains open. Preview is not production acceptance.
Network Fingerprinter — passive OS and application fingerprinting from network traffic.
I care about local-first workflows, clear boundaries, reproducible checks, and making uncertainty visible instead of hiding it.
Explore more at Levencode Labs.




