catalog

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.

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.

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.

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.

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.

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.