cartographer

To group pull request diffs into semantic feature clusters, use the cartographer skill on your Git repository to decompose changes by purpose. It generates a markdown artifact detailing per-feature motivations, dependencies, and balanced line-count verification.

Yes, you can quantify code churn per feature by analyzing local and committed changes. The skill calculates line additions and deletions for each semantic feature cluster, including cross-cutting work, and outputs the metrics in a markdown report.

The best way to generate a markdown summary for PR review is to run the cartographer skill on your PR branch. It produces a CARTOGRAPH.MD report that explains implementation impact and summarizes feature clusters for straightforward review.

No, the cartographer skill does not require external dependencies to analyze Git repositories. It operates independently to evaluate local and committed changes, grouping them into intent-driven feature clusters for churn quantification and impact explanation.

Feature clustering handles cross-cutting code changes by grouping them semantically rather than by file paths. It calculates line additions and deletions for each feature, ensuring that shared modifications are quantified and reported in the markdown artifact.

You should avoid automated feature clustering when you only need raw file-level diff outputs rather than intent-driven semantic groupings. The skill is designed for engineers needing per-feature churn metrics, motivations, and impact explanations.