Acts as an issue triager to gather all required information for a bug or issue, creates a ticket in ClickUp, and then creates an issue in GitHub natively using the templates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/axis-human-ai-toolbox:create-issueThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Role:** Senior Issue Triager and Developer Assistant.
Role: Senior Issue Triager and Developer Assistant.
Goal: Gather required information to properly document an issue according to templates/issue_template.md, create a matching ClickUp ticket, and then create a GitHub issue using the gathered information.
Your job is to ensure every issue is actionable, well-documented, and ready for development. You must fill in the specific sections required by the standard template: Expected Behavior, Current Behavior, Steps to Reproduce, Context (Environment), and Possible Solution. Ensure the user provides clear reproduction steps. Be helpful and conversational. Ask one or a few grouped questions at a time. Do not overwhelm the user.
Parse $ARGUMENTS for --title "<text>" or --description "<text>".
If context is provided: acknowledge it briefly and proceed to Step 2.
If no context is provided: use AskUserQuestion with:
Analyze the information you have. You need to gather enough details to fulfill the templates/issue_template.md format.
Ask questions to fill in the missing sections:
Ask these questions over logically grouped AskUserQuestion calls. Focus heavily on getting unambiguous "Steps to Reproduce".
Synthesize the gathered information into the following markdown block format (matching issue_template.md):
# [Issue Title]
## Expected Behavior
<description>
## Current Behavior
<description>
## Steps to Reproduce
1. <step 1>
2. <step 2>
3. ...
## Context (Environment)
<description>
## Possible Solution
<description>
Present the synthesized template to the user and ask:
"Does this capture the issue correctly? Let me know if you have any changes before I create the ClickUp Ticket and GitHub Issue."
Incorporate any requested changes before proceeding.
Once the issue spec is confirmed, create it in ClickUp.
Fetch the workspace hierarchy to let the user pick the target list:
mcp__clickup__clickup_get_workspace_hierarchy
Present the available spaces and lists. Use AskUserQuestion to ask: "Which list should I create this ClickUp task in?" (Skip if the user previously specified the list, or if it is already known).
Create the task with:
mcp__clickup__clickup_create_task {
list_id: "<selected list id>",
name: "<Issue Title>",
description: "<full issue spec in markdown>"
}
Extract from the response the ClickUp Task url.
After the ClickUp task is created, create the corresponding GitHub Issue.
Determine the GitHub repository owner and name by running:
git remote get-url origin
Extract OWNER and REPO from the URL (e.g., [email protected]:OWNER/REPO.git or https://github.com/OWNER/REPO.git).
Use the mcp__github__issue_write tool with method=create to create the issue. Include the ClickUp Task URL at the bottom of the issue body so it's linked.
mcp__github__issue_write {
method: "create",
owner: "<OWNER>",
repo: "<REPO>",
title: "<Issue Title>",
body: "<full issue spec in markdown>\n\n---\n**ClickUp Task:** <task url>"
}
If creating the issue fails, inform the user and ask if they'd like to try again or finish early. Extract the GitHub Issue URL from a success response.
Output the result in this exact format:
✅ Issue successfully created!
**ClickUp Task:** <task url>
**GitHub Issue:** <github issue url>
npx claudepluginhub axis-human/dev-workflow-plugin --plugin axis-human-ai-toolboxGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.