export-open-issues

Aggregates open GitHub, Linear, and Jira issues and generates summary reports.

Updated Aug 27, 2026

Search Tags:#project management #report generation #project tracking #backlog health #issue auditing

Ready to run

npx skills add https://github.com/Perryong/knowledge-agent --skill export-open-issues-perryong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: export-open-issues
Source: https://github.com/Perryong/knowledge-agent/tree/main/.claude/skills/export-open-issues
Command: npx skills add https://github.com/Perryong/knowledge-agent --skill export-open-issues-perryong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, linear, jira, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of auditing and exporting open issues from various project trackers, providing a comprehensive view of project status with summary analysis and archival.

Core Features & Use Cases

Multi-Tracker Support: Aggregate open issues from GitHub, Linear, and Jira.
Detailed Analysis: Offers insights into issue age, priority distribution, assignee load, and more.
Custom Reports: Generate detailed reports suitable for stakeholder reporting and sprint planning.

Quick Start

Run the /export-open-issues command to audit and export open issues from your project tracker.

Frequently Asked Questions about export-open-issues

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

FAQPage Schema

How do I export open issues from GitHub, Linear, and Jira for stakeholder reporting?▼

To export open issues from GitHub, Linear, and Jira, you can aggregate them into a single view with summary statistics and health indicators. The collected data generates detailed reports suitable for stakeholder updates and sprint planning.

What is backlog health analysis and how does it track issue age and assignee load?▼

Backlog health analysis evaluates project status by calculating issue age, priority distribution, and assignee load across multiple trackers. This mechanism provides health indicators and distribution charts to identify bottlenecks in open issues.

Do I need API keys to audit open issues across GitHub, Linear, and Jira?▼

Yes, you need API keys and access to your project trackers to audit open issues across GitHub, Linear, and Jira. These credentials are required for the system to authenticate and collect data from each respective platform.

What's the best way to generate sprint planning reports from multiple project trackers?▼

The best way to generate sprint planning reports from multiple project trackers is to aggregate open issues from GitHub, Linear, and Jira, then analyze issue age and priority distribution to produce detailed custom reports.

Can I aggregate open issues from Jira and Linear into a single project tracking report?▼

Yes, you can aggregate open issues from Jira, Linear, and GitHub into a single project tracking report. The system provides multi-tracker support to offer a comprehensive view of project status with summary analysis and archival.

How to run issue auditing for GitHub repositories using automated scripts?▼

To run issue auditing for GitHub repositories, execute the designated command to collect and analyze open issues. The scripts access the project trackers via API keys to provide summary statistics and health indicators.