Import GitHub Issues

Import open GitHub issues into local Markdown story files.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill import-github-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Import GitHub Issues
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/project-gh-import-issues
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill import-github-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, gh, and includes scripts (resource) components.

What problem does it solve?

This skill solves the friction of manually tracking GitHub issues by automatically importing them into your local project as structured story files, ensuring your local backlog stays in sync with your repository.

Core Features & Use Cases

  • Automated Sync: Fetches open GitHub issues and converts them into standardized local story files.
  • Smart Mapping: Automatically maps GitHub labels to effort levels and preserves metadata like issue numbers and URLs.
  • Idempotency: Safely skips issues that have already been imported to prevent duplicates and protect local edits.

Quick Start

Run the project-gh-import-issues skill to fetch and import all open GitHub issues into your local backlog.

Frequently Asked Questions about Import GitHub Issues

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

FAQPage Schema
How do I sync GitHub issues into local markdown story files?

Syncing GitHub issues into local markdown story files requires GitHub CLI authentication and a valid git remote. This skill fetches open issues and converts their metadata into standardized local backlog entries.

What is needed to automate importing GitHub issues into a local project backlog?

Automating GitHub issue imports requires Python3, the GitHub CLI (gh), active CLI authentication, and a valid git remote configured in your local project directory to retrieve and generate files.

Can I map GitHub issue labels to local effort levels during backlog sync?

Yes, you can map GitHub issue labels to effort levels during backlog sync. The skill automatically translates remote labels into local effort attributes while preserving issue numbers and URLs.

Will importing GitHub issues again overwrite my local markdown edits?

Importing GitHub issues again will not overwrite local markdown edits. The process is idempotent, safely skipping previously imported issues to prevent duplicates and protect your local story files.

Does the GitHub issue import tool work with closed issues?

The GitHub issue import tool does not work with closed issues. It specifically targets and retrieves open GitHub issues to synchronize with your local development backlog.