How do I install the Github Issue Creator skill?

Run npx skillmds@latest add lteawoo/github-issue-creator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Issue Creator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Issue Creator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Issue Creator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Issue Creator?

lteawoo (@lteawoo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Issue Creator by lteawoo — Agent Skill

Name: Github Issue Creator
Author: lteawoo

File contents

GitHub Issue Creator

Purpose

Turn unstructured input into a GitHub issue that is ready for development.

Core Principles

Put the acceptance criteria at the top using Given/When/Then.
Separate In Scope from Out of Scope.
An issue without a validation plan, automated or manual, is not complete.
If information is missing, ask follow-up questions instead of guessing.
Replace sensitive information with placeholders such as [USER_ID] or [TOKEN].
Include at least one recommended PR label for release categorization in the issue body.

Release Label Hints

Based on .github/release.yml, PR labels determine the release category.

New Features: feat, feature, enhancement
Bug Fixes: fix, bug, bugfix
Maintenance (Chore): chore, dependencies, ci, build, refactor
Unmatched or missing labels: Other Changes

Recommended:

Include the recommended PR label in the issue.
Apply the same label on the implementation PR to avoid release-note classification gaps.

Output Format

Title

[type] one-line summary
type: feat|fix|refactor|docs|chore|test

Acceptance Criteria

Given ...
When ...
Then ...

Background or Problem

Current state
User or operational impact

Scope

In Scope
Out of Scope

Implementation Direction

Target areas or modules
Constraints and dependencies
Risks
Recommended PR label (feat|feature|enhancement|fix|bug|bugfix|chore|dependencies|ci|build|refactor)

Validation Plan

Automated validation: lint, build, test
Manual validation: key scenarios
For UI changes: screenshot checkpoints

Completion Criteria

AC satisfied
No regressions
Release impact and cautions documented

Checklist

Implementation complete
Tests complete
Regression check complete
Recommended PR label assigned or confirmed
Docs or release notes updated if needed

When Information Is Missing

Draft the issue first.
Limit follow-up questions to three.

---name: github-issue-creatordescription: Structure bug reports, requirements, logs, or screenshots into actionable GitHub issues. Use it when you need acceptance criteria, scope definition, and a validation plan.---# GitHub Issue Creator## PurposeTurn unstructured input into a GitHub issue that is ready for development.## Core Principles1. Put the acceptance criteria at the top using Given/When/Then.2. Separate In Scope from Out of Scope.3. An issue without a validation plan, automated or manual, is not complete.4. If information is missing, ask follow-up questions instead of guessing.5. Replace sensitive information with placeholders such as `[USER_ID]` or `[TOKEN]`.6. Include at least one recommended PR label for release categorization in the issue body.## Release Label HintsBased on `.github/release.yml`, PR labels determine the release category.- `New Features`: `feat`, `feature`, `enhancement`- `Bug Fixes`: `fix`, `bug`, `bugfix`- `Maintenance (Chore)`: `chore`, `dependencies`, `ci`, `build`, `refactor`- Unmatched or missing labels: `Other Changes`Recommended:1. Include the `recommended PR label` in the issue.2. Apply the same label on the implementation PR to avoid release-note classification gaps.## Output Format### Title- `[type] one-line summary`- type: `feat|fix|refactor|docs|chore|test`### Acceptance Criteria- Given ...- When ...- Then ...### Background or Problem- Current state- User or operational impact### Scope- In Scope- Out of Scope### Implementation Direction- Target areas or modules- Constraints and dependencies- Risks- Recommended PR label (`feat|feature|enhancement|fix|bug|bugfix|chore|dependencies|ci|build|refactor`)### Validation Plan- Automated validation: lint, build, test- Manual validation: key scenarios- For UI changes: screenshot checkpoints### Completion Criteria- AC satisfied- No regressions- Release impact and cautions documented### Checklist- [ ] Implementation complete- [ ] Tests complete- [ ] Regression check complete- [ ] Recommended PR label assigned or confirmed- [ ] Docs or release notes updated if needed## When Information Is Missing- Draft the issue first.- Limit follow-up questions to three.

Frequently asked questions

Github Issue Creator