From gh
Create a new GitHub issue by writing a local markdown file with YAML frontmatter. The file is auto-synced to GitHub.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gh:create-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write a markdown file in `.issues/` to create a new GitHub issue. The file will be pushed to GitHub automatically on the next Stop hook, or manually via `issue_push`.
Write a markdown file in .issues/ to create a new GitHub issue. The file will be pushed to GitHub automatically on the next Stop hook, or manually via issue_push.
Use issue-new*.md — for example:
issue-new.mdissue-new-auth-bug.mdissue-new-refactor-api.md---
title: "Issue title here"
state: open
labels:
- bug
- priority-high
milestone: 3
assignees:
- username
---
Issue body in markdown.
Only title is required. All other fields are optional.
number, url, and pulled_atissue-new*.md to issue-{number}.md.issues/ directory must exist (create it with issue_pull first, or mkdir .issues)issue_push with the .issues/ directory pathYou can add comments to a new issue file before pushing. Append a ## Comments section after the body:
---
title: "New issue"
state: open
labels: []
---
Issue body here.
## Comments
### @username — new
First comment on the new issue.
Comments with — new headings will be posted as comments on the issue after it is created.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub n0k0/claude-plugins-backalley --plugin gh