open-issue

Draft structured GitHub issues with frontmatter and tags from conversation context.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/fengqiyu0317/assassyn --skill open-issue-fengqiyu0317
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-issue
Source: https://github.com/fengqiyu0317/assassyn/tree/main/assassyn-master/.claude/skills/open-issue
Command: npx skills add https://github.com/fengqiyu0317/assassyn --skill open-issue-fengqiyu0317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams convert ongoing conversations and product discussions into well-structured GitHub issues, ensuring consistency and traceability.

Core Features & Use Cases

  • Structured issue drafting: automatically generate a formatted issue with a clear title, description, steps, and proposed solution sections.
  • Tag and parameter guidance: select appropriate tags from project conventions and suggest related labels.
  • Template enforcement: enforce a consistent frontmatter (name and description) and standardized body to aid automation and review.
  • Use Case: a product manager chats with the team and wants to file a bug report and a feature request in one go.

Quick Start

Provide the conversation context and I will draft a GitHub issue ready for submission.

Frequently Asked Questions about open-issue

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

FAQPage Schema
How do I convert a conversation into a GitHub issue?

To convert a conversation into a GitHub issue, provide the chat context to automatically draft a structured issue with a clear title, description, steps, and proposed solution sections. The tool extracts frontmatter values and enforces standardized issue formatting for immediate submission.

How do I generate consistent GitHub issue templates from chat discussions?

Generating consistent GitHub issue templates from chats works by enforcing a standardized frontmatter and body structure. It extracts required metadata like dependencies and components, automatically drafting a formatted issue that ensures traceability and consistency for project automation and review.

Can I automatically tag and add metadata to GitHub issues from product discussions?

Yes, you can automatically tag and add metadata to GitHub issues from product discussions. The drafting process selects appropriate tags based on project conventions and generates machine-readable metadata including dependencies, components, and tagging guidance directly from the conversation context.

Does this issue drafting approach work for both bug triage and feature requests?

Yes, this issue drafting approach works for both bug triage and feature requests in software development and product management. It processes the conversation context to structure the issue, allowing product managers to file both bug reports and feature requests in one go.

What is the best way to standardize GitHub issue formats across development teams?

The best way to standardize GitHub issue formats is to enforce a consistent frontmatter with name and description fields alongside a standardized body. This approach ensures every issue includes required metadata, clear steps, and proposed solutions, aiding automation and review.

Why do my GitHub issues lack consistent metadata and traceability?

Your GitHub issues lack consistent metadata and traceability because they are not generated from a standardized template. By extracting frontmatter values and enforcing a structured format with tagging guidance, this tool ensures every issue is consistently formatted and traceable.