Agent skill · software engineering · aiskillstore
create-issue
Create an issue in GitHub or Jira. Automatically detects if GitHub issues are enabled; if so creates a GitHub issue, otherwise creates a Jira issue.
Why this skill is useful
Adds executable scripts for creating issues in GitHub or Jira based on repository settings, which the AI wouldn't reliably generate on its own.
What it needs
Requires gh, git, jira installed locally. Requires github, jira account access. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Create Issue Create an issue in the appropriate tracker (GitHub Issues or Jira). Step 1: Detect Issue Tracker 1. Get repository name: basename $(git rev-parse --show-toplevel) 2. Check if GitHub issues are enabled: If true → Create GitHub issue If false → Create Jira issue 3. Determine issue type: Task, Bug, or Story 4. Check for assignee in user's request 5. Determine priority/labels based on severity --- GitHub Issues If GitHub issues are enabled, use gh issue create. Step 2a: Write issue body to issue-body.md Use the appropriate template based on issue type (see Templates section below). Note: This file will be deleted after the command runs. Step 2b: Run gh command Add --assignee "<username>" if user specified an assignee. Note: No repo name prefix needed - GitHub issues are already scoped to the repository. --- Jira Issues If GitHub issues are disabled, use jira issue create. Step 2a: Write issue body to issue-body.md Use the appropriate template based on issue type (see Templates section below). Note: This file will be deleted after the command runs. Step 2b: Run jira command Add --assignee "<username>" if user specified an assignee. --- Templates Choose the appropriate template based on issue type: Template: Task --- Template: Bug --- Template: Story --- Priority Mapping (Jira only) Severity Jira Priority -------- ------------- Critical Blocker High Critical Medium Major Low Minor Info Minor Important Rules GitHub Issues: Use gh issue create with --body-file No repo name prefix needed (issues are scoped to repo) Labels are simple strings (e.g., bug, enhancement, documentation) Jira Issues: Always prefix summary with repo name: [repo-name] Brief description Always use --no-input flag to prevent interactive prompts Do NOT specify a project (-p or --project) - use default from user's config Set 15 second timeout - if it hangs, the command is malformed Both: Use Markdown format Use ## for main headings, - for bullet points Use backticks for inline code For sectio …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/create-issue