git-changes-reporter

Git change reports convert raw commits into JSON and Markdown using `node .claude/skills/git-changes-reporter/scripts/generate-json.js <old_commit> <new_commit>`. This produces machine-readable structured data with commit details, file references, code snippets, and metadata fields for code reviews, release notes, and CI/CD pipelines.

Reports capture design intent, core code changes, and impact through structured metadata: commits, directory analysis, domains, risk indicators, file references with line numbers, and 5-15 line code snippets. JSON output enables machine parsing while Markdown provides human-readable summaries.

Yes. Generate JSON reports from git commit ranges, then optionally enrich with GitHub repository links using the generate-github-links script. The structured output feeds directly into changelog pipelines and release documentation workflows.

The Skill handles multi-commit ranges and monorepo structures by generating triadic reports—design intent, core changes, and impact—across projects. Validation ensures template conformance and hash authenticity for complete commit coverage.

You need git and Node.js installed. The Skill reads commit history from your repository and outputs JSON and Markdown files. No additional configuration is required beyond providing old and new commit references.

Reports provide focused code snippets, risk indicators, and semantic context (design, core changes, impact) for each commit. This eliminates manual log parsing and lets reviewers assess scope and intent quickly.