sprint-review

Generate a sprint changelog from GitHub pull requests by running a command that automatically collects PRs from the last two weeks, groups them into Features and Fixes, and outputs a formatted markdown summary for your sprint review.

Yes, you can override the default two-week time range for collecting pull requests. The sprint review changelog automatically detects a two-week window but accepts custom parameters to adjust the date range as needed.

Yes, you need jq installed to generate a markdown changelog from PRs. The skill requires the jq dependency to parse and process GitHub pull request data for categorization into Features and Fixes.

The best way to categorize merged GitHub pull requests for a sprint review is to use an automated tool that groups PRs into Features and Fixes, consolidates similar items, and formats the output into a markdown document ready for presentation.

Automatic user detection works by identifying the current authenticated GitHub user when summarizing pull requests. The skill detects your GitHub identity to filter and collect only the PRs you authored, which you can also manually override.

GitHub pull requests may not appear in the sprint review changelog if they fall outside the default two-week time range, were not authored by the detected user, or if the jq dependency is not properly installed for data processing.