OpenParable
Skip to content
← Back to skills

GH Issues

Productivity
gh-issues

GH Issues is an Agent Skill for productivity published in the Kilo-Org/kilocode repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Kilo-Org/kilocode/blob/HEAD/.kilo/skills/gh-issues/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gh-issues, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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:

TemplateWhen 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:

SurfaceProjectURL
VS Code extensionVS Code Extensionhttps://github.com/orgs/Kilo-Org/projects/25
JetBrains pluginJetbrains Pluginhttps://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.