Skill

Context

Triages GitHub issues by viewing content, determining and setting project fields (component, priority, size), issue type (Bug/Feature/Task), and milestone.

Bash

Github

Git

git-workflow

automation

npx claudepluginhub oxidian/cc-plugins --plugin oxgh

Tool Access

This skill is limited to using the following tools:

Bash(gh project:*)Bash(gh issue view:*)Bash(gh api:*)

Preview

- Current repo: !`gh repo view --json nameWithOwner --jq '.nameWithOwner'`

SKILL.md

Similar Skills

Context

Creates GitHub issues via gh CLI/API, sets types (Bug/Feature/Task), links subissues, copies parent milestones/project fields. For repo issue management.

4 tools

oxgh

github-issues

29.8k

Manages GitHub issues: create/update/read via gh api and MCP tools; supports labels, assignees, types, projects, workflows, dependencies.

8 files

awesome-copilot-refactor

github-projects

Manages GitHub Projects v2 via gh CLI: create/edit/list projects, add issues/PRs as items, manage fields, link repos, automate workflows.

2 files

beagle-core

Stats

Parent Repo Stars11

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Context

Current repo: !gh repo view --json nameWithOwner --jq '.nameWithOwner'

Getting the item ID

To set project fields, you need the project item ID (not the issue number):

gh project item-list {project_number} --owner {owner} --limit 300 --format json | jq '.items[] | select(.content.number == ISSUE_NUMBER) | .id'

Setting a project field

gh project item-edit --id {item-id} --project-id {project-id} --field-id {field-id} --single-select-option-id {option-id}

Issue types

Check if an issue type is set:

gh api repos/{owner}/{repo}/issues/{number} --jq '.type.name // empty'

Set an issue type (only if not already set):

gh api -X PATCH repos/{owner}/{repo}/issues/{number} --field type=Bug

Valid types: Bug, Feature, Task

Parent issues

Find an issue's parent (for sub-issues):

gh api graphql -f query='
{
  repository(owner: "{owner}", name: "{repo}") {
    issue(number: ISSUE_NUMBER) {
      parent {
        number
        title
      }
    }
  }
}'

Get the parent's project fields (to copy them):

gh project item-list {project_number} --owner {owner} --limit 300 --format json | jq '.items[] | select(.content.number == PARENT_NUMBER)'

Milestones

Check current milestone:

gh api repos/{owner}/{repo}/issues/{number} --jq '.milestone.title // empty'

Set a milestone (use the milestone number, not title):

gh api -X PATCH repos/{owner}/{repo}/issues/{number} --field milestone={milestone-number}

Your task

Based on the user's request:

View the issue to understand its scope: gh api repos/{owner}/{repo}/issues/{number} --jq '{title, body, type: .type.name}'
Get the project item ID for the issue
Determine appropriate Component, Priority, Size, and Type (if not set) based on the issue content
Set all project fields using gh project item-edit
If the issue type is not set, set it using gh api -X PATCH
If the user specified a milestone in their request, set it using gh api -X PATCH
You have the capability to call multiple tools in a single response. Chain independent calls together.