Issue Create

Overview

Create a GitHub Issue with a structured body using one of two templates: product-backlog (parent issue) or feature (work item). The script validates input, builds the body from the selected template, and creates the issue via gh issue create.

Execution order: determine type -> compose content -> confirm with user -> create issue. Execute the script from the git repository root, not from the skill directory.

Input

• •type: string (required): Issue type, passed as --type. Must be product-backlog or feature. See references/type-reference.md.
• •repo: string (optional): Target repository, passed as --repo OWNER/REPO. Defaults to the current repository.
• •labels: string (optional): Comma-separated labels, passed as --labels.
• •assignees: string (optional): Comma-separated assignees, passed as --assignees.
• •project: string (optional): Project name, passed as --project.

Content is provided via stdin JSON:

{
  "title": "string (required)",
  "overview": "string (product-backlog)",
  "details": "string",
  "goal": "string",
  "notes": "string (product-backlog)",
  "related_urls": "string (feature)"
}

Body structure per type: references/product-backlog-template.md, references/feature-template.md.

Output

• •url: string: URL of the created issue returned by gh issue create.
• •With --json: { "number": number, "url": string }.

Operations

Determine Type

Ask the user which issue type to create (product-backlog or feature). Infer from context when the intent is clear.

Compose Content

Prepare title and body fields based on the selected template. For product-backlog, compose overview, details, goal, and notes. For feature, compose related URLs, goal, and details.

Confirm with User

Present the composed issue content to the user and get explicit approval before creating. Do not create without that confirmation.

Create Issue

Run scripts/create-issue.sh with --type and optional metadata flags. Pipe the composed JSON payload (matching the Input schema) through stdin.

The script validates the JSON, builds the body from the template, and creates the issue via gh issue create. On success it prints the issue URL to stdout.

For invocation patterns, see the Examples section.

Examples

• •Happy: user wants a product-backlog issue for a new auth feature -- title and body composed, user approves, issue created with a returned URL.
• •Failure: title is empty in the stdin JSON payload -- validation fails and the issue is not created.

cat <<'EOF' | bash scripts/create-issue.sh --type product-backlog --labels "backlog"
{
  "title": "User authentication system",
  "overview": "Implement user authentication to support login and registration flows.",
  "details": "Use OAuth 2.0 with JWT tokens for session management.",
  "goal": "Users can sign up, log in, and maintain authenticated sessions.",
  "notes": "Consider rate limiting for login endpoints."
}
EOF

cat <<'EOF' | bash scripts/create-issue.sh --type feature --repo "owner/repo" --labels "feature" --assignees "@me"
{
  "title": "Implement login endpoint",
  "related_urls": "- parent: #42",
  "goal": "POST /api/login returns a valid JWT token for correct credentials.",
  "details": "Validate email and password against the user store. Return 401 for invalid credentials."
}
EOF