git:issue

Creates GitHub issues from PRs, Slack messages, or ad-hoc descriptions with duplicate detection.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/kellymears/agents --skill git-issue-kellymears
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git:issue
Source: https://github.com/kellymears/agents/tree/main/plugins/git/skills/git-issue
Command: npx skills add https://github.com/kellymears/agents --skill git-issue-kellymears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning scattered requests from pull requests, Slack conversations, or quick verbal descriptions into well-structured, trackable GitHub issues is tedious and often produces duplicates or vague tickets. This Skill standardizes issue creation with conventional-commit-style titles, structured bodies, and duplicate checks. ## Core Features & Use Cases - Multi-source issue drafting: Builds issues from PR references (via gh pr view), pasted Slack messages, or plain descriptions, extracting the core problem from conversational noise. - Duplicate detection: Checks PR-linked issues and searches existing open issues before drafting, surfacing potential matches for confirmation. - Structured output: Generates conventional-commit-style titles (bug, feat, docs, task), a body template with context and acceptance criteria, and label suggestions mapped to existing repo labels. - Use Case: A teammate pastes a Slack complaint about a slow dashboard filter. The Skill drafts bug(dashboard): date range filter causes slow load times with context and acceptance criteria, confirms with you, then creates the issue via gh issue create. ## Quick Start Ask the assistant to create a GitHub issue from a PR number, a pasted Slack message, or a plain description of a bug or feature request.

Frequently Asked Questions about git:issue

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

FAQPage Schema
How do I create a GitHub issue from a pull request?▼

Reference the PR number or URL and the Skill reads it with `gh pr view`, checks for already-linked issues, and drafts a new issue capturing the problem or follow-up work. It confirms the draft with you before running `gh issue create`.

How do I turn a Slack message into a GitHub issue?▼

Paste the Slack message and the Skill extracts the core problem, stripping conversational filler, then drafts a titled issue with context and acceptance criteria. It credits the Slack source in the body without pasting sensitive content verbatim.

Does it check for duplicate issues before creating one?▼

Yes. It searches open issues with `gh issue list --search` using key terms and inspects PR closing-issue references. Potential matches are surfaced for your confirmation before any new issue is created.

What title format does the issue creator use?▼

Titles follow conventional commit style: `type(scope): concise description`, where type is one of bug, feat, docs, or task. This keeps titles scannable in long issue lists.

Can it assign labels and assignees automatically?▼

It suggests labels by listing existing repo labels with `gh label list` and mapping to them, but presents suggestions for your confirmation. It never assigns users without asking first.