status-reporter

Generate progress summaries from GitHub Issues, Pull Requests, and project boards.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/cmbays/mokumo --skill status-reporter-cmbays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-reporter
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/status-reporter
Command: npx skills add https://github.com/cmbays/mokumo --skill status-reporter-cmbays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive progress reports from GitHub data, providing clear insights into what has been completed, what is in progress, and any potential blockers.

Core Features & Use Cases

  • Automated Reporting: Generates detailed summaries of shipped items, in-progress tasks, and blocked issues.
  • Velocity Tracking: Analyzes historical data to show project velocity trends.
  • Milestone Progress: Reports on the completion status of current milestones.
  • Use Case: At the end of a development cycle, use this Skill to automatically generate a report detailing all issues closed, PRs merged, and the overall progress towards the current milestone, ready for review before a milestone meeting.

Quick Start

Generate a status report for the last 7 days, including PRs and velocity.

Frequently Asked Questions about status-reporter

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

FAQPage Schema
How do I generate a progress report from GitHub Issues and Pull Requests?

To generate a progress report from GitHub Issues and Pull Requests, this Skill automatically surfaces shipped items, in-progress work, blocked tasks, and velocity trends. It requires gh CLI authentication and repository access to retrieve and summarize the data.

Can I track project velocity trends using GitHub project boards?

Yes, you can track project velocity trends by analyzing historical data from GitHub project boards. This Skill evaluates closed issues and merged PRs to calculate velocity metrics for your stakeholder updates and milestone meetings.

Do I need gh CLI authentication to report on GitHub milestones?

Yes, you need gh CLI authentication and access to the target repository to retrieve data for reporting on GitHub milestones. This access allows the Skill to read issues, PRs, and project board data to determine completion status.

What is the best way to summarize blocked issues and in-progress work for stakeholder updates?

The best way to summarize blocked issues and in-progress work for stakeholder updates is to automate data extraction from GitHub. This Skill compiles closed issues, merged PRs, and milestone progress into a comprehensive summary ready for review.

How does automated GitHub reporting handle milestone progress tracking?

Automated GitHub reporting handles milestone progress tracking by analyzing the completion status of current milestones. It surfaces shipped items and blocked tasks from issues and PRs, providing clear insights into overall project progress.

Why does GitHub project velocity tracking require repository access?

GitHub project velocity tracking requires repository access because the Skill uses the gh CLI to read historical issues and pull requests. Without proper authentication and access permissions, it cannot retrieve the data needed to calculate trends.