Create a GitHub Issue for yamada-ui. Use when the user says they want to create an issue, report a bug, request a feature, report a documentation problem, or file an issue against yamada-ui.
Create a GitHub Issue for yamada-ui.
Use tools to interact with the user throughout the process.
Enter planning mode (required)
Discover available templates
.github/ISSUE_TEMPLATE/ directory in the repository and list English templates (excluding .ja.yml files)name and required fieldsConfirm issue type
Collect information
Ask for all required fields from the selected template
Ask follow-up questions to gather concrete details, code snippets, and URLs
For the "PR intent" field, offer three options (separate from the template's Yes/No):
| Option | Description | Template value | Label |
|---|---|---|---|
| Yes | Will create a PR | Yes | none |
| No | Will not create a PR | No | triage |
| Open to contributors | Open as a community contribution opportunity | Yes | good first issue |
If "Open to contributors" is selected, append the following to the issue body:
This issue is open to community contribution.
Search for existing issues (duplicates, related, parent/child candidates)
Search by keyword to find duplicates, related issues, and parent/child candidates:
gh api "search/issues?q=repo:yamada-ui/yamada-ui+<keywords>&per_page=20" \
--jq '.items[] | {number: .number, title: .title, state: .state, url: .html_url}'
Autonomously determine the relationship for each result found:
| Judgment | Condition | Action |
|---|---|---|
| Duplicate | Content is nearly identical | Abort and present the existing issue URL to the user |
| Parent/child (existing is parent) | Existing issue is a tracking issue; new issue is a subtask | Link new issue as a child via addSubIssue API |
| Parent/child (new is parent) | New issue is a tracking issue; existing issue is a subtask | After creating the new issue, link existing issue as a child via addSubIssue API |
| Depends on | New issue requires the existing one to be resolved first | Append Depends on #xxxx to the issue body |
| Related | Same component or area | Append Related #xxxx to the issue body |
| Unrelated | Different content | Do nothing |
To get the Node ID of an existing issue:
gh api repos/yamada-ui/yamada-ui/issues/{issue_number} --jq '{node_id: .node_id, title: .title}'
Autonomously determine Type and Labels
Fetch available Types:
gh api graphql -f query='{ repository(owner: "yamada-ui", name: "yamada-ui") { issueTypes(first: 20) { nodes { name description } } } }'
Fetch available Labels:
gh api repos/yamada-ui/yamada-ui/labels --paginate --jq '.[] | {name: .name, description: .description}'
Apply labels based on the PR intent answer from step 4:
Yes → no additional label; automatically assign the issue to the current user (use --assignee @me in gh issue create)No → add triageOpen to contributors → add good first issueDesign parent/child structure for multiple issues
Present plan for user review
sub-issue, Related, Depends on)yamada-ui/yamada-uigh issue create command for each issue (all flags filled in — required)Use this template for each command:
gh issue create \
--repo yamada-ui/yamada-ui \
--title "<title>" \
--body "<body>" \
--type "<Type>" \
--label "<label1>,<label2>" \
[--assignee @me] # Only if PR intent is Yes
For the ai-used checkboxes field in the template: because this skill is AI-driven by definition, copy the options exactly as written in the template into --body, with the "checked the generated content" option set to [x] and the "did not use AI" option set to [ ].
Create and link issues after approval
gh issue create commands specified in the plan — do NOT reconstruct themSub-issue linking (for both new and existing issues):
# Get parent issue Node ID
gh api repos/yamada-ui/yamada-ui/issues/{parent_issue_number} --jq '.node_id'
# Write and execute the GraphQL mutation
cat > /tmp/add_sub_issue.graphql << 'EOF'
mutation AddSubIssue($issueId: ID!, $subIssueUrl: String!) {
addSubIssue(input: { issueId: $issueId, subIssueUrl: $subIssueUrl }) {
issue { number title }
subIssue { number title }
}
}
EOF
gh api graphql \
-F query=@/tmp/add_sub_issue.graphql \
-F issueId="<parent Node ID>" \
-F subIssueUrl="https://github.com/yamada-ui/yamada-ui/issues/<child_issue_number>"