git:load-issues

You can export GitHub issues to Markdown files by running a skill that fetches all open issues via the gh CLI and saves each one as a separate file under ./specs/issues. This enables offline review, reporting, and documentation without manual copying.

Exporting GitHub issues to Markdown includes rich metadata such as the issue number, title, state, createdAt, updatedAt, author, labels, assignees, and URL. This ensures the exported files are comprehensive enough for audits and sharing with non-GitHub users.

Yes, you need the gh CLI to download GitHub issues for offline documentation. The skill relies on the gh CLI and standard shell commands to query repository issues, create directories, render per-issue metadata, and generate a summary report.

Yes, you can bulk export all open GitHub issues for reporting. The skill retrieves every open issue from the current repository and generates one Markdown file per issue with a consistent naming scheme, making it ideal for offline access and status sharing.

The best way to archive GitHub issues into a portable format is to export them as human-readable Markdown files. This approach preserves key issue metadata in a consistent directory structure under ./specs/issues, allowing non-GitHub users to review the data directly.