GitHub issue admin operations. Use when transferring issues, pinning, locking discussions, creating dev branches from issues, bulk ops, or managing custom fields.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
GitHub issue admin operations. Use when transferring issues, pinning, locking discussions, creating dev branches from issues, bulk ops, or managing custom fields.
Transferring, pinning, locking, or bulk-editing GitHub issues
Use github-issue-writing to compose a single issue body well
Creating a development branch from an issue (gh issue develop)
Use git-branch-pr-workflow for general branch + PR design
Updating custom issue fields (priority, severity, custom selects) in bulk
Use github-labels for label-only operations on issues and PRs
Performing bulk operations across many issue numbers in one command
Use git-triage to evaluate issues and PRs by completion evidence and CI state
Context
Git remotes: !git remote -v
Open issues are fetched during execution (requires a configured git remote).
Parameters
Parse $ARGUMENTS[0] as the operation, remaining args as issue numbers and options.
Issue references accept bare numbers, #N, or full GitHub issue URLs
(https://github.com/<owner>/<repo>/issues/<N>): strip a leading #, and for a
URL extract the trailing /issues/<N> number (require trailing digits — a
/pull/<N> is not an issue). When a URL's <owner>/<repo> differs from the
current remote, pass -R <owner>/<repo> to the gh calls for that issue.
Operation
Syntax
Description
transfer
transfer <N> <target-repo>
Transfer issue to another repository
pin
pin <N...>
Pin issues to repository (max 3)
unpin
unpin <N...>
Unpin issues
lock
lock <N...> [--reason <reason>]
Lock issue discussions
unlock
unlock <N...>
Unlock issue discussions
develop
develop <N> [--branch <name>] [--checkout]
Create branch from issue
bulk
bulk <sub-op> <N...> [options]
Bulk operations on multiple issues
fields
fields <N> [--set <field>=<value>] [--list]
Manage custom issue fields
Lock reasons: off-topic, too heated, resolved, spam
Bulk sub-operations: label, assign, close, reopen
When to Use
Use this skill when...
Use X instead when...
Transferring issues between repos
Creating new issues (github-issue-writing)
Pinning/unpinning important issues
Implementing issue fixes (git:issue)
Locking resolved discussions
Managing sub-issues/deps (git:issue-hierarchy)
Creating dev branches from issues
Searching for issues (github-issue-search)
Bulk labeling/assigning/closing
Auto-detecting related issues (github-issue-autodetect)
Setting custom field values
Execution
Execute the requested issue management operation.
Step 1: Parse Operation and Validate
Parse the operation from $ARGUMENTS[0]. Validate that specified issue numbers exist:
# Create branch and switch to it locally
gh issue develop $N --checkout
# Create branch with custom name
gh issue develop $N --name $BRANCH_NAME --checkout
# Create branch without checkout
gh issue develop $N
The branch name defaults to {issue-number}-{issue-title-slug}. The branch is automatically linked to the issue on GitHub.
Bulk Operations
Apply the same operation to multiple issues at once.
Bulk label:
# Pre-check: create any missing labels before applyingfor LABEL in $(echo"$LABELS" | tr',''\n'); doif ! gh label list --search "$LABEL" --json name | jq -e ".[] | select(.name==\"$LABEL\")" >/dev/null 2>&1; thenecho"Label '$LABEL' not found — skipping (create it first with: gh label create \"$LABEL\")"
LABELS=$(echo"$LABELS" | sed "s/,$LABEL//;s/$LABEL,//;s/^$LABEL$//")
fidonefor N in$ISSUE_NUMBERS; do
[ -n "$LABELS" ] && gh issue edit $N --add-label "$LABELS"done
Bulk assign:
for N in$ISSUE_NUMBERS; do
gh issue edit $N --add-assignee "$USERS"done
Bulk close:
for N in$ISSUE_NUMBERS; do
gh issue close $Ndone
Bulk reopen:
for N in$ISSUE_NUMBERS; do
gh issue reopen $Ndone
Report success/failure count after bulk operations.
Custom Fields
Manage custom issue fields (requires org-level issue field configuration).
List available fields:
# Get org name from repo
ORG=$(gh repo view --json owner --jq '.owner.login')
# List fields
gh api orgs/$ORG/issue-fields --jq '.[] | "\(.id): \(.name) (\(.type))"'
Get field values for an issue:
gh api repos/$OWNER/$REPO/issues/$N/issue-field-values \
--jq '.[] | "\(.field.name): \(.value)"'
Set a field value:
FIELD_ID=$(gh api orgs/$ORG/issue-fields --jq '.[] | select(.name == "$FIELD_NAME") | .id')
gh api repos/$OWNER/$REPO/issues/$N/issue-field-values \
-X POST -f field_id=$FIELD_ID -f value="$VALUE"
If the repo is not in an organization, report: "Custom issue fields require an organization-level repository."
