github-status

Summarize GitHub activity across repositories, issues, and pull requests.

25|5|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Nimbalyst/skills --skill github-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-status
Source: https://github.com/Nimbalyst/skills/tree/main/skills/product/github-status
Command: npx skills add https://github.com/Nimbalyst/skills --skill github-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps Product Managers and developers quickly understand and report on GitHub activity, progress, and status across repositories, issues, and pull requests, saving time on manual status aggregation.

Core Features & Use Cases

  • Repository Summaries: Get overviews of open issues, PR activity, milestones, and contributor stats.
  • Team Progress Tracking: Understand what team members are working on, identify blockers, and track sprint progress.
  • Feature/Epic Status: Consolidate all related work items for a specific feature or epic.
  • Stale Work Detection: Identify and flag items that have stalled or require attention.

Quick Start

Summarize the current status of the 'nimbalyst-api' repository, focusing on open issues by priority and active PRs awaiting review.

Frequently Asked Questions about github-status

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

FAQPage Schema
How do I summarize GitHub activity across multiple repositories for status updates?

To summarize GitHub activity for status updates, you can aggregate repository-level metrics, open issues, and active pull requests across your project. This process scopes repository summaries and team workload to identify blockers and track sprint progress efficiently.

What is the best way to track team progress and identify blockers in GitHub issues and pull requests?

Tracking team progress and identifying blockers in GitHub issues and pull requests requires consolidating contributor stats and flagging stale or blocked items. This approach monitors team workload and highlights work that has stalled or requires immediate attention.

Can I consolidate GitHub issues and PRs to report on a specific feature or epic status?

Yes, you can consolidate GitHub issues and pull requests to report on a specific feature or epic status. This process groups related work items together, providing a clear overview of feature progress and milestone completion for project reporting.

How do I detect stale or blocked GitHub pull requests and issues that need attention?

Detecting stale or blocked GitHub pull requests and issues involves analyzing activity timestamps and review states to flag items that have stalled. This identification highlights active PRs awaiting review and issues requiring immediate attention to keep projects moving.

Does this GitHub reporting approach require any external project management dependencies?

No, this GitHub reporting approach operates without external project management dependencies. It directly summarizes activity, metrics, and contributor stats from your existing GitHub repositories, issues, and pull requests to generate project status reports.