__create-issue

Create repository issues from user requests with template and duplicate detection.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cilly-yllic/.llm --skill create-issue-cilly-yllic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: __create-issue
Source: https://github.com/cilly-yllic/.llm/tree/main/skills/ja/__create-issue
Command: npx skills add https://github.com/cilly-yllic/.llm --skill create-issue-cilly-yllic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a user's sometimes multi-part request into actionable repository issues that follow the target repo's rules and templates while reducing duplicate submissions.

Core Features & Use Cases

  • Service-aware issue creation: Detects the appropriate issue management service (e.g., GitHub Issues, Linear, Jira, Notion) based on the target repo’s LLM files, skills, docs, and tooling, and then uses that service’s conventions.
  • Rule-respecting drafting: Collects templates and repository rules (including labels and existing structure when available) and generates issue titles/bodies accordingly.
  • Multi-item handling with confirmation: If the input contains multiple matters, proposes categorization and splitting, then asks for user approval before creating multiple issues.
  • Duplicate detection workflow: By default, searches for similar existing issues and asks the user whether to append, merge, create anew, or skip, with an option to skip checks when explicitly requested and allowed by repo rules.

Quick Start

Ask the AI to create repository issues from your request with duplicate checking and service/template detection by saying: /__create-issue "Add a bug report for login failing on Safari and include expected behavior and reproduction steps".

Frequently Asked Questions about __create-issue

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

FAQPage Schema
How do I create GitHub Issues or Linear tasks that automatically follow repository templates and labels?

To create repository issues that respect templates and labels, the Skill detects the target issue management service automatically and drafts titles and bodies according to the repo's specific conventions and contribution rules.

How do I split a multi-part request into separate issues across different issue management services?

For multi-item inputs, the Skill proposes categorization and splitting, then asks for user confirmation before creating multiple issues across services like GitHub Issues, Linear, Jira, and Notion.

What is the best way to detect and prevent duplicate issue creation in repositories?

To prevent duplicate issue creation, the Skill searches for similar existing issues by default and asks whether to append, merge, create anew, or skip, applying repo-specific constraints.

Can I skip duplicate detection when creating bug reports or feature requests?

You can skip duplicate checks when explicitly requested and allowed by repository rules, allowing direct issue creation for bug reports and feature requests without searching existing tickets.

Does this approach work with Jira and Notion in addition to GitHub Issues?

Yes, service-aware issue creation detects the appropriate issue management service, including GitHub Issues, Linear, Jira, and Notion, based on the target repository's LLM files, docs, and tooling.