export-open-issues

Collect, analyze, and report open issues from GitHub, Linear, and Jira.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Boboegg/COG-second-brain --skill export-open-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-open-issues
Source: https://github.com/Boboegg/COG-second-brain/tree/main/.claude/skills/export-open-issues
Command: npx skills add https://github.com/Boboegg/COG-second-brain --skill export-open-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of auditing and exporting open issues from project trackers, providing summary analysis and vault archival for project status tracking.

Core Features & Use Cases

  • Project Tracking Audit: Summarizes and archives open issues from GitHub, Linear, and Jira.
  • Data Analysis: Provides insights on issue age, priority distribution, and assignee load.
  • Use Case: Before a sprint planning session, use this Skill to get a comprehensive overview of the current open issues in all project trackers.

Quick Start

Run the command: /export-open-issues

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 Jira, Linear, and GitHub for a backlog audit?

You can export open issues by running the `/export-open-issues` command, which automates collection and summary analysis across GitHub, Linear, and Jira to provide actionable backlog health insights.

What is the best way to analyze project backlog health before sprint planning?

Analyzing backlog health is best done by auditing issue age, priority distribution, and assignee load across project trackers. This Skill automates that data collection and provides a comprehensive overview for sprint planning.

Does this issue tracking audit require API access to GitHub, Linear, and Jira?

Yes, this issue tracking audit requires API access to GitHub, Linear, and Jira to automate the collection of open issues and perform project status tracking and data analysis.

Can I assess assignee load and issue priority distribution across multiple project trackers?

Yes, you can assess assignee load and issue priority distribution across multiple project trackers. The Skill aggregates open issues from GitHub, Linear, and Jira to deliver these specific data analysis insights.

How do I automate stakeholder reporting for project status tracking?

Automate stakeholder reporting by running the `/export-open-issues` command, which summarizes open issues and archives the project status data for stakeholder clarity and tracking.

When do I need to archive open issues from project trackers?

You need to archive open issues from project trackers when preparing for a sprint planning session or when you require a permanent vault record of backlog health for ongoing project status tracking.