t1k:issue

Create GitHub issues for bugs and feature requests with deduplication.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t1k:issue
Source: https://github.com/tranvietanh0/StackTheRing/tree/main/.claude/skills/t1k-issue
Command: npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of reporting bugs and feature requests directly to GitHub repositories, reducing duplication and streamlining the workflow.

Core Features & Use Cases

  • Bug Reporting: Automatically creates and tracks issues for reported bugs in GitHub repositories.
  • Feature Requests: Suggest new features or enhancements for GitHub projects.
  • Use Case: When encountering a bug or a feature that could improve a project, use this Skill to create an issue with all necessary details.

Quick Start

Run the /t1k:issue skill with the command "Invoke the /t1k:issue skill.

Affected skill/agent: <skill-name> Absolute path: <path to affected file> Origin metadata (from frontmatter/JSON/comment): - kit: <kit-name> - repository: <owner/repo> - module: <module-name or null> Label: <bug|gotcha|enhancement> Description: <what is wrong or needed> Context: <error encountered, fix applied locally, expected vs actual>

Run the full /t1k:issue workflow:

  1. Pre-flight checks (GitHub MCP or gh CLI)
  2. Duplicate check (search existing open issues)
  3. If duplicate: add_issue_comment instead of creating new
  4. Else: create issue with the template in this skill
  5. Report the issue URL or comment URL back."

Frequently Asked Questions about t1k:issue

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

FAQPage Schema
How do I automatically create GitHub issues for bug reporting?

You can automatically create GitHub issues for bug reporting by running a skill that uses GitHub CLI tools to generate issues with predefined templates. It performs pre-flight checks, searches for duplicate open issues, and creates a new issue or adds a comment if a duplicate exists.

What's the best way to report feature requests to GitHub repositories without duplicates?

The best way to report feature requests without duplicates is to use an automated issue creation workflow that checks existing open issues before submitting. If a matching feature request is found, it adds a comment to the existing issue instead of creating a new one.

Do I need GitHub CLI installed to automate issue creation?

Yes, you need GitHub CLI installed and properly configured with GitHub access to automate issue creation. The workflow relies on the gh CLI or GitHub MCP to perform pre-flight checks, search existing issues, and create new issues.

How does duplicate detection work when submitting bug reports to GitHub?

Duplicate detection for bug reports works by searching existing open GitHub issues before creating a new one. If the workflow finds a matching issue, it uses add_issue_comment to append to the existing thread instead of creating a duplicate issue.

Can I use GitHub MCP instead of the gh CLI for issue management?

Yes, you can use GitHub MCP instead of the gh CLI for issue management. The skill performs pre-flight checks during its workflow to verify whether GitHub MCP or the gh CLI is available and properly configured before proceeding with issue creation.

What information is needed to report a bug using automated GitHub issue creation?

To report a bug using automated GitHub issue creation, you need to provide the affected skill name, absolute file path, origin metadata, label, description, and context. This structured information is formatted into a template to generate a complete GitHub issue.