How do I install the Gh Issues skill?

Run npx skillmds@latest add gabrielmoreira/gh-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 Gh Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh 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 Gh Issues free to use?

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

Who published Gh Issues?

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

Gh Issues by gabrielmoreira — Agent Skill

Name: Gh Issues
Rating: 4.5 (4 reviews)
Author: gabrielmoreira

Gh Issues

Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via `gh`. Covers issue templates, project board assignment, title conventions, and required `gh` scopes.

gabrielmoreira Updated Sep 21, 2026 17 repo stars

File contents

GitHub Issues

Use this skill whenever you create or manage a GitHub issue with gh for either the VS Code extension or the JetBrains plugin.

Templates

The repo defines issue templates in .github/ISSUE_TEMPLATE/. Pick the matching template instead of opening a blank issue:

Template	When to use
`Bug report` (`bug-report.yml`)	Reproducible defects with steps, expected, and actual behavior
`Feature Request` (`feature-request.yml`)	New capabilities, enhancements, or behavior changes
`Question` (`question.yml`)	Usage or design questions that aren't obviously bugs or feature requests

Pass the template title to gh issue create --template.

Title Conventions

Use a plain, descriptive title that reads cleanly as a standalone sentence.
Do not add platform-specific prefixes such as [JetBrains], [Jetbrains], [JB], [VS Code], [VSCode], or similar. Routing happens through project boards, not the title.

Project Boards

Every new issue must land on the correct project board:

Surface	Project	URL
VS Code extension	`VS Code Extension`	https://github.com/orgs/Kilo-Org/projects/25
JetBrains plugin	`Jetbrains Plugin`	https://github.com/orgs/Kilo-Org/projects/39

Pass the project title to gh issue create --project.

Recipes

Create a VS Code extension bug report and add it to the board:

gh issue create \
  --template "Bug report" \
  --project "VS Code Extension" \
  --title "Sidebar chat fails to render after reload" \
  --body "..."

Create a JetBrains feature request:

gh issue create \
  --template "Feature Request" \
  --project "Jetbrains Plugin" \
  --title "Support Kotlin Multiplatform target detection" \
  --body "..."

Scope Errors

If gh reports a missing scope when assigning a project, refresh the auth token and retry:

gh auth refresh -s project

After the refresh succeeds, re-run the original gh issue create command. Do not fall back to creating the issue without the project — the board assignment is required.

---name: gh-issuesdescription: Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via `gh`. Covers issue templates, project board assignment, title conventions, and required `gh` scopes.---# GitHub IssuesUse this skill whenever you create or manage a GitHub issue with `gh` for either the VS Code extension or the JetBrains plugin.## TemplatesThe repo defines issue templates in `.github/ISSUE_TEMPLATE/`. Pick the matching template instead of opening a blank issue:| Template | When to use ||---|---|| `Bug report` (`bug-report.yml`) | Reproducible defects with steps, expected, and actual behavior || `Feature Request` (`feature-request.yml`) | New capabilities, enhancements, or behavior changes || `Question` (`question.yml`) | Usage or design questions that aren't obviously bugs or feature requests |Pass the template title to `gh issue create --template`.## Title Conventions- Use a plain, descriptive title that reads cleanly as a standalone sentence.- Do not add platform-specific prefixes such as `[JetBrains]`, `[Jetbrains]`, `[JB]`, `[VS Code]`, `[VSCode]`, or similar. Routing happens through project boards, not the title.## Project BoardsEvery new issue must land on the correct project board:| Surface | Project | URL ||---|---|---|| VS Code extension | `VS Code Extension` | https://github.com/orgs/Kilo-Org/projects/25 || JetBrains plugin | `Jetbrains Plugin` | https://github.com/orgs/Kilo-Org/projects/39 |Pass the project title to `gh issue create --project`.## RecipesCreate a VS Code extension bug report and add it to the board:```bashgh issue create \ --template "Bug report" \ --project "VS Code Extension" \ --title "Sidebar chat fails to render after reload" \ --body "..."```Create a JetBrains feature request:```bashgh issue create \ --template "Feature Request" \ --project "Jetbrains Plugin" \ --title "Support Kotlin Multiplatform target detection" \ --body "..."```## Scope ErrorsIf `gh` reports a missing scope when assigning a project, refresh the auth token and retry:```bashgh auth refresh -s project```After the refresh succeeds, re-run the original `gh issue create` command. Do not fall back to creating the issue without the project — the board assignment is required.

Frequently asked questions