grove-issues

Parses unstructured text into GitHub issues with labels and bodies.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill grove-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grove-issues
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/grove-issues
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill grove-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill transforms unstructured lists of tasks, ideas, or to-dos into well-defined, actionable GitHub issues, streamlining project management and reducing the burden of manual issue creation.

Core Features & Use Cases

  • Automated Issue Creation: Parses brain dumps into discrete GitHub issues.
  • Smart Labeling: Assigns relevant component, pattern, and type labels based on content.
  • Duplicate Detection: Checks for and flags existing issues to prevent redundancy.
  • Structured Issue Bodies: Generates issues with clear summaries, acceptance criteria, and context.
  • Use Case: You have a meeting transcript with several action items. This Skill can convert those action items into individual GitHub issues, complete with appropriate labels and a clear structure for developers to follow.

Quick Start

Use the grove-issues skill to turn the following list into GitHub issues: fix login bug, add user profile page, improve search performance.

Frequently Asked Questions about grove-issues

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

FAQPage Schema
How do I turn unstructured text into GitHub issues automatically?

To turn unstructured text into GitHub issues, this Skill parses brain dumps or meeting transcripts into discrete issues with structured bodies, acceptance criteria, and smart labels. It automates task conversion to streamline project management workflows directly through the GitHub CLI.

How does duplicate issue detection work when parsing tasks into GitHub?

Duplicate issue detection works by checking existing GitHub issues during task conversion to prevent redundancy. It flags matching entries found in the repository before creating new issues, ensuring your project management tracking remains clean and free of duplicate tickets.

Do I need GitHub CLI and jq to create issues from text?

Yes, you need GitHub CLI (gh) and jq installed to use this task conversion workflow. The Skill requires GitHub CLI for repository issue interaction and jq for data processing to parse text and manage structured issue creation.

What is the best way to convert meeting action items into structured GitHub issues?

The best way to convert meeting action items into structured GitHub issues is parsing the transcript into individual tickets with clear summaries and context. This Skill assigns relevant component and type labels automatically while generating actionable bodies for developers.

Can I assign component and type labels when automating GitHub issue creation?

Yes, you can assign component and type labels when automating GitHub issue creation. The Skill features smart labeling that analyzes the parsed text content and automatically assigns relevant pattern, component, and type labels to each generated issue.