github-sprint-tracker

Generate sprint summary reports for GitHub pull requests without Jira tickets.

Updated Jul 22, 2023
One-click install
npx skills add https://github.com/ValerianGuivarch/lsr-nestjs-backend --skill github-sprint-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-sprint-tracker
Source: https://github.com/ValerianGuivarch/lsr-nestjs-backend/tree/main/.claude/skills/github-sprint-tracker
Command: npx skills add https://github.com/ValerianGuivarch/lsr-nestjs-backend --skill github-sprint-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires md-to-pdf, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of sprint summary reports for GitHub pull requests that do not reference Jira tickets, saving time and reducing manual efforts.

Core Features & Use Cases

  • Sprint Summary Report: Generates a report listing all pull requests created or merged during a sprint that do not reference a Jira ticket.
  • Markdown and PDF Export: Produces the report in both Markdown and PDF formats for easy sharing and review.
  • GitHub and Jira Integration: Requires GitHub and Jira MCP to be configured for proper operation.
  • Use Case: Ideal for project managers or team leads who need to quickly summarize sprint progress without manually reviewing each pull request.

Quick Start

Generate a sprint summary report for Sprint 36 by using the command: 'generate sprint summary for Sprint 36'.

Frequently Asked Questions about github-sprint-tracker

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

FAQPage Schema
How do I generate a sprint summary report for GitHub pull requests without Jira tickets?

You can generate a sprint summary report by using a command like 'generate sprint summary for Sprint 36'. The Skill fetches and filters pull requests without Jira references and outputs Markdown and PDF formats.

Do I need Jira MCP configured to track pull requests missing Jira tickets?

Yes, both GitHub and Jira MCP must be configured for proper operation. The Skill uses these integrations to fetch pull requests and filter out those that do not reference a Jira ticket during the sprint.

What's the best way to automate sprint progress tracking for pull requests that lack Jira references?

Automating sprint progress tracking is best handled by generating a summary report that lists all pull requests created or merged during a sprint without a Jira ticket, which this Skill produces in Markdown and PDF.

Can I export my GitHub sprint summary to PDF using md-to-pdf?

Yes, you can export the sprint summary to PDF. The Skill requires the md-to-pdf dependency to convert the generated Markdown report of pull requests without Jira tickets into a shareable PDF format.

Why does my sprint summary report only include pull requests without Jira tickets?

The sprint summary report specifically filters for pull requests that do not reference a Jira ticket to help project managers identify gaps in ticket tracking and quickly summarize untracked sprint progress.