How do I install the Github Issues skill?

Run npx skillmds@latest add amanahmed2222/github-issues 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 Issues 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 Issues?

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 Issues free to use?

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

Who published Github Issues?

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

Github Issues by amanahmed2222 — Agent Skill

Name: Github Issues
Author: amanahmed2222

File contents

You create, update, query, and comment on GitHub issues. Infer the project's language variant (US/UK English) from existing issues, docs, and code, and match it in all output.

Read individual rule files in rules/ for detailed requirements and examples.

Rules Overview

Rule	Impact	File
Issue title	HIGH	`rules/issue-title.md`
Template adherence	MEDIUM	`rules/template-adherence.md`
No checklists	MEDIUM	`rules/no-checklists.md`

Workflow

Determine action: create, update, query, or comment
Check if we're in a GitHub repository and get owner/repo info
Check for issue templates in .github/ISSUE_TEMPLATE/ or .github/
List available organisation issue types (fails for user-owned repos — expected, proceed without)
For creation or update:
- For updates: fetch the current issue first
- When issue types are available, select the most appropriate type (e.g. Bug for defects, Feature for new functionality, Task for general work)
- Generate title following rules/issue-title.md
- Generate body following template if found (see rules/template-adherence.md), otherwise use clear structured format
- For creation: get the current authenticated user and include in assignees
- If the user specifies a parent issue, link the created/updated issue as a sub-issue (use the issue's node ID, not its number)
For parent/sub-issue management:
- To list sub-issues: get the parent issue's sub-issues
- To add a sub-issue: pass the parent issue number and the child's node ID
- To remove a sub-issue: unlink the child from the parent
- To reorder sub-issues: reprioritise with after_id or before_id
- When creating multiple related issues, prefer structuring them as a parent with sub-issues rather than flat independent issues
For queries:
- Fetch a specific issue by number
- Inspect sub-issue hierarchy on a parent issue
- Search issues for filters, keywords, and cross-repo lookups
- List repository issues
For comments:
- Fetch issue context first when needed
- Add the comment to the issue
Display a summary with issue links and what changed

Validation

For titles: follow rules/issue-title.md
For body with template: follow rules/template-adherence.md
For labels: only use labels that already exist in the repository
For assignees: only assign valid repository collaborators

---name: github-issuesdescription: Use when filing a bug, requesting a feature, creating an issue, or updating issue details. Manages GitHub issues with templates, formatting, and auto-assignment.---You create, update, query, and comment on GitHub issues. Infer the project's language variant (US/UK English) from existing issues, docs, and code, and match it in all output.Read individual rule files in `rules/` for detailed requirements and examples.## Rules Overview| Rule | Impact | File ||------|--------|------|| Issue title | HIGH | `rules/issue-title.md` || Template adherence | MEDIUM | `rules/template-adherence.md` || No checklists | MEDIUM | `rules/no-checklists.md` |## Workflow1. Determine action: create, update, query, or comment2. Check if we're in a GitHub repository and get owner/repo info3. Check for issue templates in `.github/ISSUE_TEMPLATE/` or `.github/`4. List available organisation issue types (fails for user-owned repos — expected, proceed without)5. For creation or update: - For updates: fetch the current issue first - When issue types are available, select the most appropriate type (e.g. Bug for defects, Feature for new functionality, Task for general work) - Generate title following `rules/issue-title.md` - Generate body following template if found (see `rules/template-adherence.md`), otherwise use clear structured format - For creation: get the current authenticated user and include in assignees - If the user specifies a parent issue, link the created/updated issue as a sub-issue (use the issue's **node ID**, not its number)6. For parent/sub-issue management: - To list sub-issues: get the parent issue's sub-issues - To add a sub-issue: pass the parent issue number and the child's node ID - To remove a sub-issue: unlink the child from the parent - To reorder sub-issues: reprioritise with `after_id` or `before_id` - When creating multiple related issues, prefer structuring them as a parent with sub-issues rather than flat independent issues7. For queries: - Fetch a specific issue by number - Inspect sub-issue hierarchy on a parent issue - Search issues for filters, keywords, and cross-repo lookups - List repository issues8. For comments: - Fetch issue context first when needed - Add the comment to the issue9. Display a summary with issue links and what changed## Validation- For titles: follow `rules/issue-title.md`- For body with template: follow `rules/template-adherence.md`- For labels: only use labels that already exist in the repository- For assignees: only assign valid repository collaborators

Frequently asked questions

Github Issues