create-github-issue

name	Create Github Issue
description	Load this skill when creating a GitHub project backlog issue or drafting an issue title, body, type, or labels.

Create Github Issue

Create project backlog items as GitHub Issues and add them to the Bean Lab GitHub Project.

Project Target

Created issues must be added to the Bean Lab GitHub Project:

• Project URL: https://github.com/orgs/beanlab/projects/13/views/1
• Project owner: beanlab
• Project number: 13

The token must include the project scope. Check with gh auth status; add it with gh auth refresh -s project if needed. If gh auth status reports an invalid environment token, verify that the specific gh command fails before stopping. Some environments have an invalid GITHUB_TOKEN while another authenticated path still lets the necessary command complete.

Issue Types and Labels

Every issue must have a GitHub issue type:

• Touch Code - any work that involves the code
• Task - something that needs doing, but doesn't involve changing code

For labels, add needs-clarification only when the input is ambiguous or incomplete.

Title Rules

• Use a short imperative summary.
• Do not write a full sentence.
• Prefer concise, action-oriented phrasing when the issue represents work to do.

Body Template

Use this issue body template:

Created on: <YYYY-MM-DD>
Created by: <user>

## Details

<Overview of the item. Capture the problem, intent, and details
currently known.>

## Out-of-scope

<Changes or features left for other backlog items. Reference related
issues when known.>

## Dependencies

<Other backlog issues this item depends on. Reference related issues
when known.>

Creation Workflow

• Create issues automatically once enough input exists; do not add a confirmation step.
• Assign the best-fit GitHub issue type.
• If the human owner is known but their GitHub username is not, record the owner in the issue body and do not guess an assignee. Assign the issue only when the username is known.
• Creating a backlog issue is about capturing the ideas immediately on hand, not fleshing out the idea or preparing for implementation.
• Draw relevant information from the conversation when drafting the issue.
• Think through what information should and should not be included.
• If input is ambiguous but there is enough to create a placeholder, create the issue, add needs-clarification, and fill the body using best-effort inference.
• Prefer --body-file for multi-line bodies.
• Always add the created issue to Bean Lab project 13.
• If the available gh issue create or gh issue edit commands cannot set the issue type directly, use the GitHub UI or an appropriate GitHub API call to set the issue type. Do not consider issue creation complete until the GitHub issue type is set.

Create the issue with the correct GitHub issue type, then add it to the project:

issue_url="$(gh issue create \
  --title "<title>" \
  --body-file <body-file>)"
# Set the GitHub issue type to `Task` or `Touch Code`, then add it.
gh project item-add 13 --owner beanlab --url "$issue_url"

For unclear input, add the clarification label:

issue_url="$(gh issue create \
  --title "<title>" \
  --label "needs-clarification" \
  --body-file <body-file>)"
# Set the GitHub issue type to `Task` or `Touch Code`, then add it.
gh project item-add 13 --owner beanlab --url "$issue_url"

If gh issue create and gh issue edit cannot set the GitHub issue type directly, use the GraphQL API.

Find the repository issue type ID:

gh api graphql \
  -f query='query {
    repository(owner:"beanlab", name:"myteam") {
      issueTypes(first:20) {
        nodes { id name }
      }
    }
  }'

Find the issue node ID:

gh issue view <issue-number-or-url> \
  --json id,number,url

Set the issue type:

gh api graphql \
  -f query='mutation($id:ID!, $type:ID!) {
    updateIssue(input:{id:$id, issueTypeId:$type}) {
      issue { number issueType { name } }
    }
  }' \
  -f id=<issue-node-id> \
  -f type=<issue-type-id>

Use the target repository in the issue-type query when creating issues outside beanlab/myteam.

Priority

Backlog priority is a GitHub Project field, not an issue label. When the user asks for a priority during issue creation, add the issue to the project first, then update the project item.

Use these current IDs for the Bean Lab backlog project:

• Project ID: PVT_kwDOCA0Mqs4BW0Oo
• Priority field ID: PVTSSF_lADOCA0Mqs4BW0OozhSFeN8
• P0 option ID: 79628723
• P1 option ID: 0a877460
• P2 option ID: da944a9c

Find the project item, then set the requested priority:

gh project item-list 13 \
  --owner beanlab \
  --format json \
  --jq '.items[] | select(.content.number == <issue-number>)'

gh project item-edit \
  --id <project-item-id> \
  --project-id PVT_kwDOCA0Mqs4BW0Oo \
  --field-id PVTSSF_lADOCA0Mqs4BW0OozhSFeN8 \
  --single-select-option-id <priority-option-id>

If the fixed IDs stop working, refresh them with gh project field-list 13 --owner beanlab --format json --limit 100.

Output

After successful issue creation and project insertion, output only the GitHub issue URL or issue number/ID. Do not return the issue body or metadata after creation.

If issue creation succeeds but adding the issue to the project fails, report the issue URL and the project-add error.