create-issue

Original：🇨🇳 Chinese

Translated

Create GitHub Issues with a parent-child structure (sub-issues). Generate parent and child issues using `gh issue create`, and link the parent-child relationship with `gh api .../sub_issues`. It is recommended to use Conventional Commits format (`feat:`, `fix:`, etc.) for titles. Used for scenarios like "Create an Issue" and "Break down tasks into Issues".

2installs

Sourcefandhe-ai/agent-cli-skills

Added on2026-05-11

NPX Install

npx skill4agent add fandhe-ai/agent-cli-skills create-issue

SKILL.md Content (Chinese)

View Translation Comparison →

create-issue

Create GitHub Issues with a parent-child structure.

Prerequisites

The
```
gh
```
CLI is installed and authenticated
Can be verified with
```
gh auth status
```

Flow

Step 1: Analyze the task content

Extract the following from the user's description:

Overview of the feature/fix
Background/motivation
Acceptance criteria
Breakdown into individual tasks

Step 2: Create the parent Issue

bash

gh issue create \
  --title "feat: Feature Name" \
  --body "$(cat <<'EOF'
## Overview
...

## Background
...

## Acceptance Criteria
- [ ] Criteria 1
- [ ] Criteria 2

## Related
- Figma: ...
- Related Issue: #...
EOF
)"

Titles should follow the Conventional Commits format:

feat:

,

fix:

,

chore:

, etc.

Step 3: Create child Issues

Create each individual task as a child Issue:

bash

gh issue create \
  --title "feat: Task Name" \
  --body "..."

Step 4: Link as sub-issues

Use

gh api

to add child Issues to the parent's sub-issues:

bash

gh api \
  --method POST \
  repos/{owner}/{repo}/issues/{parent_number}/sub_issues \
  -f sub_issue_id={child_number}

Step 5: Return Issue URLs

Display a list of URLs for the created parent and child Issues.

Notes

It is recommended to use Conventional Commits format for Issue titles
Child Issues should be granular enough to be completed independently
Confirm with the user if labels/milestones are needed
Use
GIT_SSL_NO_VERIFY=1
in sandbox environments: Refer to the "Execution in sandbox environments" section below for details

Execution in sandbox environments

When executing this skill in a sandbox environment, consider using

GIT_SSL_NO_VERIFY=1

for GitHub operations over the network. The main remote operations of this skill are

gh issue create

/

gh api

, and the "remote write" determination is Required (this skill mainly uses APIs). For details on command classification and precautions for disabling TLS verification, refer to

docs/sandbox-tls.md

.

create-issue

NPX Install

Tags

SKILL.md Content (Chinese)

create-issue

Prerequisites

Flow

Step 1: Analyze the task content

Step 2: Create the parent Issue

Step 3: Create child Issues

Step 4: Link as sub-issues

Step 5: Return Issue URLs

Notes

Execution in sandbox environments