changelog

When this skill is invoked:

1. Read the argument for the target version or sprint number. If a version is given, use the corresponding git tag. If a sprint number is given, use the sprint date range.

1b. Check git availability — Verify the repository is initialized:

• Run git rev-parse --is-inside-work-tree to confirm git is available
• If not a git repo, inform the user and abort gracefully

2. Read the git log since the last tag or release:

   git log --oneline [last-tag]..HEAD
   

   If no tags exist, read the full log or a reasonable recent range (last 100 commits).

3. Read sprint reports from production/sprints/ for the relevant period to understand planned work and context behind changes.