Track your product by feature, not by commit
How CodeMD maps your product's features to the code, tags every commit with the features it worked on, and shows feature progress on a dashboard. Works locally with the free VS Code plugin and on GitHub with the PR checks app. (1:48)
Dashboard views are example data for a fictional product. The GitHub check is a real CodeMD Feature Impact result.
Read the transcript
Track your product's progress by feature, not by commit.
You think in features. Your code is a stream of commits. CodeMD connects the two, automatically.
Building on your own machine? The free VS Code plugin maps each feature to the real functions behind it, and shows how much is built and how many tests pass.
Building on GitHub? The CodeMD PR checks app names the feature a pull request touches. It traces the changed code up through its callers to your product's entry points, so the feature is found automatically.
Your dashboard then tags every commit with the features it worked on. Solid tags are named in the commit message. Dashed tags are found from the code itself. Planning commits are counted as plans, never as progress.
The feature progression table shows each feature's status, completion, passing tests, and the commits behind it.
Program managers and leaders see which features moved this month, and which have not, without reading a single commit.
Under the hood, the call graph links features to code. Each commit's changed functions are matched to those features, and the results roll up into progress per feature.
Use the free VS Code plugin locally, or install the PR checks app on GitHub. Either way, you track product progress by feature.
Know what your team built. Feature by feature.