sprint-report

Generates sprint reports by analyzing Git history and issue tracker data.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/jholhewres/devclaw-skills --skill sprint-report-jholhewres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-report
Source: https://github.com/jholhewres/devclaw-skills/tree/main/skills/sprint-report
Command: npx skills add https://github.com/jholhewres/devclaw-skills --skill sprint-report-jholhewres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of comprehensive sprint reports by consolidating data from Git and issue tracking systems, saving development teams significant manual effort.

Core Features & Use Cases

  • Data Aggregation: Collects commits, merged PRs, closed issues, and open issues within a specified sprint period.
  • Report Structuring: Organizes collected data into key sections like Velocity, Completed Items, Carry-over, Blockers, and Metrics.
  • Use Case: A team lead can use this skill at the end of a two-week sprint to quickly generate a report detailing what was accomplished, what remains, and key performance indicators, facilitating smoother sprint reviews and planning.

Quick Start

Use the sprint-report skill to generate a report for the last two weeks of activity.

Frequently Asked Questions about sprint-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an agile sprint report from git history and issue tracker data?

Generating an agile sprint report from git history and issue tracker data involves collecting commits, merged PRs, and closed issues within a specific sprint period. This process aggregates development metrics to track team velocity and identify carry-over items.

What is included in a sprint report when tracking development metrics with GitHub CLI?

A sprint report tracking development metrics with GitHub CLI includes commits, merged pull requests, closed issues, and open issues. It structures this data into sections like velocity, completed items, carry-over, blockers, and performance metrics.

Can I use bash scripting to automate sprint velocity tracking for my development team?

You can use bash scripting to automate sprint velocity tracking by leveraging git and gh CLI commands. This approach queries repository history and issue tracker data to calculate velocity and identify blockers for development teams.

Does the sprint report skill work with GitHub CLI for issue tracking and PR aggregation?

The sprint report skill works directly with GitHub CLI for issue tracking and PR aggregation. It uses gh commands to collect merged pull requests, closed issues, and open issues within a specified sprint period to generate structured output.

What's the best way to identify carry-over items in agile project management reports?

The best way to identify carry-over items in agile project management reports is by comparing closed issues against open issues within a sprint period. Analyzing git history and issue tracker data isolates incomplete tasks for the next sprint planning phase.