CodeMD now names the feature behind every change
When a commit lands, a manager's first question is rarely "which function changed?" It's "which feature is this, and how is that feature coming along?" CodeMD's Feature Impact check now answers the first half on its own: it works out which feature the change belongs to, names it, and explains what was modified or added. Nobody has to write a feature list first.

What the check tells you
Everything below comes from the check in the screenshot. It was produced for a small commit that added one helper script.
- Change impact: 16/100 · LocalizedHow far the change reaches. A small change with no callers reads as localized.
- Changed: 2 functions in 1 fileWhat was modified or added, in plain counts.
- Affected callers: 0 reachable functionsWhether other code depends on what changed.
- CodeMD-discovered feature: Marketing Site & DocsThe feature this change belongs to, found without a feature list.
- Mapped automatically from: changed code → callers → repository entry pointsHow it got there: it follows the call graph from the changed functions up to the places the repository starts running.
- Relevant tests: none foundWhether any test reaches the change. Here none did, and the check says so plainly.
- Recommended next action"Add or run a focused test for the highest-impact changed path."
Below those fields, the check explains the discovery in a sentence anyone can read: which functions changed, how many calls up they are reached from, and that no existing test reaches the change.
Why this helps the people who manage the work
- Every commit lands against a named feature. Instead of a list of file paths, a manager sees which feature is being worked on, so activity can be followed feature by feature.
- Each change comes with an explanation. Which functions changed, how widely the change reaches and what it was mapped from are written out, not left for someone to reconstruct from a diff.
- Gaps are visible early. "No existing test reaches this change" appears on the commit itself, so an untested area shows up while it's cheap to fix.
- There is nothing to maintain. The feature is derived from the repository's own call graph, so it keeps up as the code changes.
An honest note on the name
The feature name is an inference, which is why the check shows Confidence: Medium here. CodeMD found it by following the code, not by asking you. If you want your team's own words instead, say so once:
CodeMD inferred this feature from the repository because it has no product & features list. Add a .codemd/product_vision.json (synced from codemd.dev) to use your team's own feature names.
See it on your own commits
Install the GitHub app, push a change, and open the checks list. Feature Impact appears alongside Call-Path Security and Impacted Tests. Access to your code is read-only, and your tests run in your own GitHub Actions.
Know which feature each change belongs to
Free to install. CodeMD gives your team information about risk paths and feature impact; it doesn't block attacks or replace a security program.
Install free on GitHub