issues

Aggregate issue and pull request statistics from GitHub and GitLab APIs.

1|Updated May 5, 2026

Search Tags:#GitHub #issue tracking #statistics #project health #GitLab

One-click install

npx skills add https://github.com/ecosyste-ms/skills --skill issues-ecosyste-ms

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: issues
Source: https://github.com/ecosyste-ms/skills/tree/main/skills/issues
Command: npx skills add https://github.com/ecosyste-ms/skills --skill issues-ecosyste-ms

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of accessing and analyzing issue and pull request metadata across various forges, enabling users to gauge project health and maintainability.

Core Features & Use Cases

Forge Metadata Analysis: Gather stats on issues and PRs from GitHub, GitLab, and other platforms.
Project Health Assessment: Determine responsiveness, average time to close, and merge rates.
Use Case: For a project maintainer looking to assess their project's health and improve issue management.

Quick Start

Analyze issue and PR statistics for the 'rails/rails' repository using the issues skill.

Frequently Asked Questions about issues

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

FAQPage Schema

How do I analyze GitHub and GitLab issue statistics to assess project health?▼

To analyze GitHub and GitLab issue statistics, you can aggregate issue and pull request metadata to assess project health, responsiveness, and maintainability. This requires network access to forge APIs and processes JSON data formats to present actionable insights.

What metrics are used to measure project maintainability through issue tracking?▼

Project maintainability is measured by aggregating issue tracking statistics such as average time to close, merge rates, and community engagement responsiveness. These metrics help maintainers identify bottlenecks and improve issue management workflows across various forges.

Can I use this tool to gather pull request statistics for the rails/rails repository?▼

Yes, you can gather pull request statistics for repositories like rails/rails by accessing forge APIs. The tool aggregates and presents PR metadata to help developers seeking insights into codebase health and community engagement.

Do I need network access to aggregate issue and PR metadata from multiple forges?▼

Yes, network access to forge APIs is required to aggregate issue and PR metadata from GitHub, GitLab, and other platforms. The tool fetches and processes JSON data formats to deliver comprehensive statistics for project health assessment.

What's the best way to track responsiveness and merge rates across different code repositories?▼

The best way to track responsiveness and merge rates is by aggregating issue and pull request statistics across GitHub, GitLab, and other forges. This approach streamlines access to metadata, enabling maintainers to gauge project health and improve issue management.