create-issue

Create GitHub issues from conversation context with templates and project mapping.

4|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill create-issue-agmo-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/create-issue
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill create-issue-agmo-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the end-to-end creation of GitHub Issues from conversation context or user input, including automatic mapping to project boards and templates to ensure consistency and faster turnaround.

Core Features & Use Cases

  • Auto-map new issues to GitHub Projects and select the appropriate feature, task, or bug template.
  • Generate well-structured issue bodies based on org templates and recommended sections.
  • Supports linking parent features for tasks and resolves assignee to the current user.

Quick Start

Instruct the AI to create a GitHub Issue from the current discussion context using the defined issue templates and project integration.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I automate GitHub issue creation from a conversation context?

Automating GitHub issue creation involves applying organization templates and project integration to map discussion context into structured issue bodies, resolving assignees, and linking parent tasks automatically.

Can I auto-map new GitHub issues to project boards and apply templates?

Yes, auto-mapping new GitHub issues to project boards supports selecting the appropriate feature, task, or bug template to generate well-structured issue bodies based on predefined organization templates.

How does template-driven GitHub issue generation handle parent linkage for tasks?

Template-driven GitHub issue generation supports linking parent features for tasks, resolving the assignee to the current user, and ensuring proper issue type mapping through safety checks.

Do I need GitHub project integration to ensure correct issue type mapping?

GitHub project integration is required to ensure correct project association and proper issue type mapping, applying safety checks during the end-to-end issue creation process.

What is the best way to generate well-structured GitHub issue bodies from org templates?

Generating well-structured GitHub issue bodies from org templates is best handled by automating the extraction of conversation context into recommended sections, ensuring consistency and faster turnaround.

Why does auto-assigning a GitHub issue to the current user fail without safety checks?

Auto-assigning a GitHub issue requires safety checks to verify correct project association and proper issue type mapping, preventing errors during the end-to-end creation process.