Run the tests that matter for your change in VS Code, before it is committed.
Automated Pre-commit Test Creation and Execution for AI-written Code
Know what your change breaks.
Before you commit.
CodeMD maps your codebase into the product features it implements. On every change, it finds the tests that matter for the features you touched—creates the ones that are missing—and runs them before you commit.
Free VS Code extension. CodeMD analyzes without changing your source.
3 features touched by this change
2 files · 4 functions changed · not yet committed
Your tests know about functions.
Your users care about features.
Most tools tell you a test failed. CodeMD tells you which part of your product you were about to break—because it knows how every function maps to a feature.
Every change, checked against the features it touches.
As you or your coding agent edit code, CodeMD detects each changed and new function, follows the call graph to the features it affects, reuses the most relevant existing tests, creates the ones that are missing, and runs that focused set in VS Code—before anything is committed.
See how focused testing works →The feature map is what makes the tests right.
Connect your repository once. CodeMD builds the call graph, reads repository evidence, and maps every function to the product feature it implements. Nothing to configure. A generic test runner sees changed files—CodeMD sees that you just touched Billing controls, and which tests protect it.
Map your repository →Mapped to 18 functions across authentication, invitations, and workspace setup · 12 tests.
Detected from dashboards, event aggregation, exports, and analytics routes · 4 tests.
Mapped to 21 functions across invoices, plans, and payment webhooks · 15 tests.
Guardrails for your coding agent.
CodeMD’s MCP server gives Claude Code and other MCP-compatible agents the callers, impact radius, and covering tests for a function before they edit it—and the exact tests to run before they call the change done. Every AI-written change arrives with evidence.
Test AI-written code →7 callers · 2 features affected: Billing controls, Usage reporting.
4 functions changed · 5 tests to verify · 1 changed function without coverage.
Every commit becomes feature progress.
The same feature map turns commits into a daily view your whole team can read. See which features changed, where tests fell behind, which defects are open, and what is ready to ship—without reconstructing the story from tickets and diffs.
See daily feature progress →3 functions changed · 2 tests added · export sub-feature updated
SSO callback updated · 8 affected tests passed
All mapped functions tested · no open defects
Evidence for developers. Progress for everyone.
Developers commit knowing what they touched and that it still works. Product and engineering leads see every feature move, every day.
Unit, contract, integration, and regression tests created where coverage is missing.
Every function mapped to the product feature it implements, from your call graph.
Follow changes, test movement, defects, and readiness by feature, every day.
Commit with evidence, not hope.
Install the free VS Code extension and run the tests that matter for your next change.