whats-new

You can generate a changelog from git diffs by fetching from origin, running git log and git diff against a target branch, parsing changed files for models, services, tasks, APIs, and migrations, and writing a dated markdown summary to .notes/changelog.

The best way to summarize recent git commits for code review is to analyze branch differences, highlight new files and modified modules, and identify areas of architectural significance like models, services, tasks, APIs, and migrations to produce a scannable summary.

Yes, you can create release notes from git branch differences by comparing HEAD against a target branch or time range to produce a structured markdown changelog entry summarizing commits, new capabilities, modified files, and dependency changes.

Yes, this changelog generation approach works without external dependencies, relying solely on standard git commands like fetch, log, and diff to analyze repository changes and output a markdown file.

You need to run a git diff analysis for a changelog entry after merging a feature branch, during handoffs, or when catching up on recent development activity to create a concise summary for release notes or onboarding.