issue-filing

Create structured issue files for unresolved framework problems under patterns/$GITHUB_USER/issues/.

9|10|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/jkomoros/community-patterns --skill issue-filing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-filing
Source: https://github.com/jkomoros/community-patterns/tree/main/.claude/skills/issue-filing
Command: npx skills add https://github.com/jkomoros/community-patterns --skill issue-filing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured way to document and escalate complex framework issues or architectural questions to framework authors. It ensures all necessary context and failed attempts are captured, preventing wasted time and facilitating quicker resolutions.

Core Features & Use Cases

  • Structured Issue Template: Guides the creation of detailed issue files, including problem summaries, use cases, failed attempts with code, and specific questions. This ensures comprehensive reporting.
  • Escalation Path: Clearly defines when to file an issue (after exhausting other recovery strategies) and emphasizes the need for user permission, ensuring issues are a last resort.
  • Framework Author Communication: Formats issues to be highly informative for framework maintainers, speeding up diagnosis and feedback, and leading to faster solutions.
  • Use Case: After trying multiple approaches and consulting all available documentation for a persistent framework-related problem, and with user permission, use this skill to create a comprehensive issue file that clearly outlines the problem and all your attempts for framework authors to review.

Quick Start

I've exhausted all recovery strategies for a complex framework issue. The user has given permission to file an issue. Use the issue-filing skill to create a new issue file for 'Reactive Computed Timing'.

Frequently Asked Questions about issue-filing

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

FAQPage Schema
When should I file a framework issue instead of troubleshooting on my own?

File a framework issue after exhausting documentation, trying multiple recovery approaches, and confirming with the user. Issues document suspected bugs, edge cases, or architectural questions that framework authors need to review, preventing wasted effort and accelerating resolution.

How do I document a complex framework bug for maintainers to review?

Create a detailed issue file using the structured template: summarize the problem, describe your use case, document all failed attempts with code, and pose specific questions. This comprehensive format helps framework authors diagnose and respond faster.

What should I include when reporting a framework issue?

Include a problem summary, use case context, all failed recovery strategies with code examples, and targeted questions for framework authors. The issue template enforces this structure, ensuring maintainers receive complete information to diagnose the root cause.

How do I organize and name framework issue files?

Use the ISSUE naming convention and create files as ISSUE-Brief-Title.md under patterns/$GITHUB_USER/issues/. This standardized structure ensures issues are discoverable and follow the established workflow for framework author escalation.

Why document failed attempts before filing a framework issue?

Documenting failed approaches demonstrates you've exhausted recovery options and provides framework authors with concrete context about what doesn't work. This accelerates diagnosis, prevents duplicate issue reports, and leads to faster solutions.