CodeMD now names the feature behind every change

CodeMD · 2026-11-14 · A real check from our own repository

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.

The CodeMD Feature Impact check on GitHub: Localized impact 16/100, a CodeMD-discovered feature named Marketing Site and Docs, mapped automatically from changed code to callers to repository entry points, with no relevant tests found.
The Feature Impact check on one of our own commits, as it appears next to the Call-Path Security and Impacted Tests checks.

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.

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
What this check is and isn't. It's informational: it runs no tests and never blocks a merge. "Tests reach" means a test calls the changed code, or something that calls it, in the call graph. It doesn't mean the change is asserted. A named feature and an impact score are leads for a human to read, not a verdict on quality.

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

See the PR Checks dashboard · Watch the 1:48 walkthrough