builder-evidence

To compile git commit history for product marketing storytelling, you can automatically extract commit diffs, rationale, and technical metrics from local repositories to build verifiable evidence packs. This grounds your narrative in primary-source build history.

You extract commit diffs and design rationale for a feature release by analyzing local git repositories and project documentation for specific story clusters. This compiles technical data into a standardized evidence pack ready for content production.

Yes, you need local git repositories and design documentation to gather build history evidence. The skill performs read-only analysis of your local project files to fetch diffs, commit messages, and technical metrics for content creation.

You can automate evidence gathering from design documentation by running read-only analysis on local repositories. It automatically fetches design rationale and commit messages, compiling them into structured technical data for product marketing.

The best way to verify technical history for product storytelling is compiling primary-source evidence packs from local git repositories. This ensures marketing content is grounded in actual commits and design documentation rather than speculation.

Yes, builder-evidence works with gtm_core.journey.gitscan to perform read-only analysis of build history and project documentation. This integration is required to extract commit diffs, rationale, and technical metrics from local repositories.