skills.rest
Busboom-Foo
Busboom-FooOFFICIAL
Explore all skills by this author →
GitHub

gh-import

Convert open GitHub issues into CLASI TODOs with issue references.

Updated Apr 3, 2026
Search Tags:#automation#github#issues#workflows#import#team-workflow#clasi-todos
One-click install
npx skills add https://github.com/Busboom-Foo/meetupfu --skill gh-import
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-import
Source: https://github.com/Busboom-Foo/meetupfu/tree/main/.claude/skills/gh-import
Command: npx skills add https://github.com/Busboom-Foo/meetupfu --skill gh-import

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issues are often left unmanaged in CLASI workflows. This skill imports open issues into CLASI as TODOs with github-issue references to enable lifecycle tracking and central visibility.

Core Features & Use Cases

  • Import issues from a repository (or the current one) and create corresponding CLASI TODOs with metadata like github-issue references.
  • Filter by labels or state to target actionable items and manage scope.
  • Use cases include backlog grooming, sprint planning, and cross-repo issue tracking by mapping GitHub issues to CLASI tasks.

Quick Start

Import all open issues from a GitHub repository and generate CLASI TODOs with github-issue references.

Frequently Asked Questions about gh-import

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

FAQPage Schema
How do I import GitHub issues into CLASI as tracked TODOs?▼

You can import GitHub issues into CLASI by automatically converting open issues into TODOs with github-issue references. This process fetches issues, enables user-guided selection, and generates YAML TODOs with proper metadata for lifecycle tracking.

Can I import issues from multiple repositories into CLASI?▼

Yes, importing GitHub issues into CLASI supports cross-repo imports as well as local repository imports. This allows you to map open issues from various repositories into centralized CLASI TODOs for cross-repo issue tracking.

What is the best way to manage GitHub issue backlogs using CLASI?▼

The best way to manage GitHub issue backlogs in CLASI is importing open issues as TODOs with github-issue references. This enables backlog grooming and sprint planning by providing central visibility and lifecycle tracking for actionable items.

How do I filter GitHub issues when importing them to CLASI TODOs?▼

You can filter GitHub issues by labels or state when importing them to CLASI TODOs. Filtering by labels or state allows you to target actionable items and manage scope during backlog grooming or sprint planning workflows.

Does importing GitHub issues into CLASI require access verification?▼

Yes, importing GitHub issues into CLASI requires access verification as part of its end-to-end workflow. The process includes argument parsing, access verification, fetching issues, user-guided selection, and YAML TODO creation to ensure secure imports.

Why are my GitHub issues left unmanaged in CLASI workflows?▼

GitHub issues are often left unmanaged in CLASI workflows because they lack proper tracking. Importing open issues as CLASI TODOs with github-issue references solves this by enabling lifecycle tracking and central visibility across repositories.

Related Skills

Explore More Software Engineering Skills→
busboom-software-studiobusboom-software-studio
1

gh-import

Import GitHub issues into CLASI TODOs with label filtering.

Official
Advanced
hmzainjamilhmzainjamil
1

Jira Automation

Automate Jira issue management, sprint planning, and workflow transitions.

Community
Advanced
Busboom-FooBusboom-Foo

report

Report bug details to the ericbusboom/clasi GitHub repository via API or gh CLI.

Official
Intermediate
ChatAndBuildChatAndBuild
1

gh-issues

Triage and prioritize GitHub issues with labels, SLA, and templates.

Official
Advanced