Skip to content
@levencode-labs

Levencode Labs

Thoughtful developer tools, built with AI and refined through engineering.
Levencode Labs logo

Levencode Labs

Thoughtful tools for working with code.

Built with AI. Refined through engineering, testing, and review.


We build practical tools for developers and coding agents. The aim is simple: make complex code changes easier to understand, safer to carry out, and clearer to verify.

Products: BlastRadius · Deploom · SelfReview · Migrator

BlastRadius

BlastRadius B radar mark

See what a change touches. Find what becomes unreachable.

BlastRadius gives developers and coding agents an evidence-backed map of a refactor's potential impact. Before a change, it traces static symbol consumers, React components, affected routes and related tests. After a change, it finds newly unreachable exports and broken references against a Git baseline.

  • Trace the impact. Inspect file- and symbol-level dependencies, not just text matches.
  • Spot the leftovers. Separate newly orphaned code from existing dead code and test/Storybook-only usage.
  • Keep uncertainty visible. Public APIs, side effects and unresolved dynamic usage never become blanket permission to delete.

Repository · Source preview · Architecture

Development preview (0.0.1-dev) — no v0.1.0 release. CLI, MCP server and Agent Skill are under validation; npm publication and complete acceptance remain pending.


Deploom

Deploom logo

Dependency upgrades with a clear plan.

Deploom helps developers and coding agents plan dependency updates for JavaScript and TypeScript projects. It brings version choices, compatibility constraints, permitted changes, and unresolved evidence into one inspectable workflow.

  • Plan within boundaries. Choose which dependencies may change and which version lines are acceptable.
  • Understand decisions. See conflicts, blockers, and the reasons behind proposed versions.
  • Check the result. Keep planning, installation, and runtime verification separate.

Get started · Руководство на русском · Latest release

Projects

RepositoryWhat it does
 Deploom Core Planning engine for dependency-version decisions, compatibility constraints, and explicit evidence.
 Deploom MCP Agent-facing MCP server, structured upgrade plans, verification boundaries, and the optional deploom-upgrade Skill.
 Deploom npm Windows installer for the MCP server and Skill, with offline setup and a public cache of npm advisories and migration records.

Deploom is under active development. An upgrade plan is not an installed or runtime-verified migration; acceptance requires checks against the actual result.


SelfReview

SelfReview logo

Project conventions you can trace, approve, and check before code review.

SelfReview is a local toolkit for JavaScript, TypeScript, and React/TSX. It turns project-specific review expectations into explicit, reusable checks: collect rule candidates from source code, agreements, and merge-request feedback; review and approve them; then apply supported rules through AST analysis, the CLI, and an ESLint adapter.

  • Respect project scopes. Keep conventions separate for each codebase or share them across a team.
  • Approve deliberately. Discovered patterns and review comments are rule candidates, not automatic policy.
  • Review before the review. Check changed code and export conventions for agents and developers.

Get started · Руководство на русском · Repository

SelfReview complements human code review. Unsupported or ambiguous conventions stay visible for manual review; AST checks do not replace project tests or runtime verification.


Migrator

Migrator geometric M mark

Move from Selenium C# NUnit to Playwright .NET, with evidence at every step.

Migrator brings a Roslyn-based .NET 10 migration engine together with an MCP server and an agent Skill. It helps developers and coding agents understand legacy tests, identify unsupported transformations, and prepare conservative Playwright drafts before independent verification.

  • Analyze first. Inspect source, dependencies, and blockers instead of blindly replacing Selenium APIs.
  • Preview carefully. Generate traceable target code and explicitly mark unsupported or ambiguous behavior.
  • Verify independently. Keep source analysis, compilation, Chromium runtime checks, and cleanup ownership separate.

Repositories

RepositoryWhat it does
 Migrator Core Roslyn-based AST analysis, migration planning and conservative Selenium C# NUnit → Playwright .NET code generation.
 Migrator MCP Agent-facing MCP server and Skill for analysis, explanation, preview, and explicit artifact verification.

Active development. The Windows Chromium lifecycle/cleanup investigation is still open (Core issue #59); a migration preview is not a production-verified migration. Both repositories are part of Levencode Labs.

Popular repositories Loading

  1. deploom-mcp deploom-mcp Public

    MCP tools and agent workflows for explainable dependency upgrades and verification.

    Python

  2. selenium-playwright-migrator-core selenium-playwright-migrator-core Public

    C#

  3. selenium-playwright-migrator-mcp selenium-playwright-migrator-mcp Public

    Python

  4. deploom-core deploom-core Public

    Headless dependency planning engine with explicit constraints, scope, and evidence.

    Python

  5. .github .github Public

  6. selfreview selfreview Public

    Local, scope-aware self-review for JavaScript and TypeScript. Learn convention candidates from code, docs, and MR feedback; approve rules and use one AST engine across CLI, ESLint, and agent workfl…

    JavaScript 1

Repositories

Showing 9 of 9 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Most used topics

Loading…