GitHub Ticket

Overview

Create, inspect, or route GitHub issues and set Diversio project-board fields with gh.

This skill ships inside the GitHub Ticket Manager plugin and can be installed through the Claude Code marketplace or directly in Codex from its skill path.

Parent Surface

When to Use This Skill

Use this Skill when you want to:

This Skill is the GitHub-native replacement for the old clickup-ticket workflow. Issue forms in monolith are a human fallback and a schema reference, not the primary creation path.

• create GitHub issues without opening the browser
• capture backlog work quickly with smart defaults
• fetch or list issues across monolith and a small repo set
• view your assigned work
• route planning work into repo-local execution issues
• add created issues to Diversio Work with the right board fields
• keep GitHub issue creation skill-driven instead of form-driven

Output Expectations

When this Skill completes a write action, always return:

When it completes a read or list action, keep the response scan-friendly and show enough context that the user does not need to open GitHub immediately.

• repo
• issue number
• title
• URL
• labels applied
• whether project add succeeded or was skipped
• which project fields were applied, skipped, or failed

Prerequisites

Before calling GitHub for the requested action:

Preferred auth model:

prefer gh auth refresh -s project

• repo for issue read/write
• read:org for org visibility
• project when project add or field hydration is expected
• normal gh login
• no plugin-specific token in the common case
• if project hydration is part of the workflow and project scope is missing, prefer gh auth refresh -s project

Default Operating Model

Treat these defaults as the steady-state baseline unless the user overrides them:

Routing rules:

DiversioTeam/monolith.

as the execution repo after normalizing the git remote into owner/repo.

DiversioTeam/monolith.

issue in that repo when issues are enabled there.

it is still valid to use that repo; do not reject it only because it is not prelisted in config.

• planning repo: DiversioTeam/monolith
• execution repos:
• DiversioTeam/Django4Lyfe
• DiversioTeam/Diversio-Frontend
• DiversioTeam/Optimo-Frontend
• DiversioTeam/diversio-ds
• DiversioTeam/infrastructure
• DiversioTeam/naboo
• DiversioTeam/diversio-serverless
• DiversioTeam/launchpad
• DiversioTeam/skiddie
• DiversioTeam/terraform-modules
• DiversioTeam/agent-skills-marketplace
• canonical IDs: native GitHub issue numbers
• legacy ClickUp GH-xxxx IDs: metadata only when applicable
• If you are in the monolith root and no repo is specified, prefer DiversioTeam/monolith.
• If you are inside a repo checkout and no repo is specified, prefer that repo as the execution repo after normalizing the git remote into owner/repo.
• If the work clearly spans repos or still needs planning, create the issue in DiversioTeam/monolith.
• If the user asks for implementation work in a specific repo, create the issue in that repo when issues are enabled there.
• If repo detection yields a GitHub repo outside the default execution list, it is still valid to use that repo; do not reject it only because it is not prelisted in config.

Resources

Declared allowed tools:

Installation

Switch between Claude Code and Codex, then copy the install command for the runtime you use.

claude plugin marketplace add DiversioTeam/agent-skills-marketplace
claude plugin install github-ticket@diversiotech

CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
python3 "$CODEX_HOME/skills/.system/skill-installer/scripts/install-skill-from-github.py" \
  --repo DiversioTeam/agent-skills-marketplace \
  --path plugins/github-ticket/skills/github-ticket

Invocation:

/github-ticket:create-issue
/github-ticket:get-issue
/github-ticket:my-issues
/github-ticket:quick-issue
/github-ticket:list-issues
/github-ticket:route
/github-ticket:configure
/github-ticket:create-linked-issue
/github-ticket:add-to-backlog

name: github-ticket