capture-issue

Parse natural language input into categorized issue files with duplicate detection.

7|2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill capture-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-issue
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/.gemini/skills/capture-issue
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill capture-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of manual issue tracking by automatically parsing natural language conversations or direct descriptions into structured, project-ready issue files.

Core Features & Use Cases

  • Intelligent Parsing: Automatically infers issue type, priority, and description from context or user input.
  • Duplicate Detection: Prevents clutter by identifying similar or exact duplicate issues using Jaccard similarity and history database checks.
  • Epic Integration: Seamlessly links new tasks to parent epics, updating documentation and tracking relationships automatically.

Quick Start

Use the capture-issue skill to create a new bug report based on the current conversation context.

Frequently Asked Questions about capture-issue

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

FAQPage Schema
How do I automate issue tracking from natural language conversations?

This skill parses natural language input or conversation history to capture and categorize software issues, automatically inferring issue type, priority, and description to generate structured project-ready issue files.

How does duplicate detection work for project issues?

Duplicate detection uses Jaccard similarity and session history database checks to identify similar or exact duplicate issues, preventing clutter and maintaining project consistency before generating template-based files.

Can I link new tasks to parent epics automatically?

Yes, you can link new tasks to parent epics automatically. The skill operates within a structured repository environment to perform epic linking, updating documentation and tracking relationships automatically.

Do I need local configuration files to maintain project consistency?

Yes, local configuration files are required. The skill requires integration with local configuration files and session history databases to maintain project consistency and state during issue capture and epic linking.

What is the best way to create bug reports from conversation context?

The best way to create bug reports from conversation context is using template-based file generation. The skill captures issues from conversation history, categorizes them, and generates structured files within a repository environment.

Why does issue tracking require a structured repository environment?

A structured repository environment is required to perform duplicate detection, template-based file generation, and epic linking while integrating with local configuration files and session history databases to maintain project state.