catalog

Convert findings into prioritized, labeled GitHub issues.

Updated Apr 17, 2026

Search Tags:#automation #github #catalog #issues #code-review #epic-label

Ready to run

npx skills add https://github.com/smallorbit/smallorbit-plugins --skill catalog-smallorbit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: catalog
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/speckit/skills/catalog
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill catalog-smallorbit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert findings into prioritized, labeled GitHub issues: $ARGUMENTS

Core Features & Use Cases

Extract discrete findings from explicit input, earlier in this conversation, or a file path.
Create GitHub issues with category and priority labels, and optional epic labeling via --epic <slug>.
Support epic-labeling workflow with optional approval prompts to ensure proper tracking.

Quick Start

Provide findings or a file path; the skill will convert them into prioritized GitHub issues.

Frequently Asked Questions about catalog

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

FAQPage Schema

How do I convert code review findings into prioritized GitHub issues?▼

You can convert code review findings into prioritized GitHub issues automatically by providing explicit input, earlier conversation context, or a file path to the tool, which then extracts findings and creates labeled issues with category and priority tags.

How do I add epic labels to GitHub issues created from extracted findings?▼

To add epic labels to GitHub issues, use the --epic <slug> flag when running the tool, which assigns the specified epic slug to the generated issues to ensure proper tracking within a larger epic workflow.

Can I automatically approve GitHub issue creation without manual prompts?▼

Yes, you can automatically approve GitHub issue creation without manual prompts by using the --auto flag, which bypasses the optional approval workflow and creates the issues directly from the extracted findings.

What sources can I use to generate GitHub issues from conversation findings?▼

You can generate GitHub issues from three sources: explicit input text, findings from earlier in the current conversation, or a file path pointing to a document containing the findings you want to catalog.

Does the issue cataloging tool support assigning priority and category labels?▼

Yes, the tool supports assigning both priority and category labels to GitHub issues during creation, ensuring that each cataloged finding is properly categorized and prioritized for tracking.

What is the best way to track code review findings as GitHub issues with epic labels?▼

The best way to track code review findings as GitHub issues with epic labels is to use a cataloging tool that extracts findings from your input source and creates prioritized, labeled issues with optional epic slug assignment via the --epic flag.