Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From arn-code
Creates issues in configured GitHub or Jira trackers with Arness labels for type and priority. Auto-activates on phrases like 'create issue', 'report bug', or 'request feature'.
npx claudepluginhub appsvortex/arness --plugin arn-codeHow this skill is triggered — by the user, by Claude, or both
Slash command
/arn-code:arn-code-create-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create an issue in the configured issue tracker (GitHub or Jira) with Arness labels for type and priority.
Browses Arness-labeled issues from GitHub, Jira, or local feature backlog, selects unblocked one via dependency resolution, and routes to implementation pipeline.
Creates and manages GitHub issues for bugs, features, and tasks with enforced quality standards like reproducibility steps, acceptance criteria, and severity assessment.
Creates well-structured GitHub issues using gh CLI with templates for bugs, features, tasks including titles, descriptions, acceptance criteria, and labels. Use for filing bugs or feature requests.
Share bugs, ideas, or general feedback.
Create an issue in the configured issue tracker (GitHub or Jira) with Arness labels for type and priority.
If no ## Arness section exists in the project's CLAUDE.md, inform the user: "Arness is not configured for this project yet. Run /arn-planning to get started — it will set everything up automatically." Do not proceed without it.
Read the Issue tracker field from ## Arness config in the project's CLAUDE.md (values: github, jira, or none). If the Issue tracker field is not present, fall back to legacy detection: check for GitHub: yes and treat as github; otherwise treat as none.
git rev-parse --is-inside-work-tree — must be inside a git repositorygit remote -v — must have a GitHub remote (origin pointing to github.com)gh auth status — the GitHub CLI must be authenticatedIf any check fails, inform the user what is missing and suggest running /arn-planning to get started. Do not proceed until all prerequisites are satisfied.
## Arness config/mcp to check status, or run /arn-planning to reconfigure."Inform the user: "Issue management is not configured for this project. Run /arn-planning to get started, or configure the issue tracker manually."
STOP — do not proceed.
Trigger message inference: If the user's trigger message contains enough context to infer the issue type, priority, and title (e.g., "create issue: high priority bug — checkout page crashes on empty cart"), extract these values and present them for confirmation rather than re-asking each question separately. If the trigger message is ambiguous, proceed with the standard question flow below.
Ask the user to select the issue type using AskUserQuestion. Present these options:
| Option | GitHub Label | Jira Issue Type | Jira Label | Description |
|---|---|---|---|---|
| Feature request | arness-feature-issue | Story | arness-feature-issue | A new feature or enhancement |
| Bug report | arness-bug-issue | Bug | arness-bug-issue | Something is broken or not working as expected |
| Backlog item | arness-backlog | Task | arness-backlog | Deferred or low-urgency item for future consideration |
The user-facing question is the same regardless of issue tracker. The internal mapping differs by platform and is applied during submission (Step 5).
Ask the user to select the priority using AskUserQuestion. Present these options:
| Option | GitHub Label | Jira Priority | Description |
|---|---|---|---|
| High | arness-priority-high | High | Urgent — should be addressed soon |
| Medium | arness-priority-medium | Medium | Important but not urgent |
| Low (default) | arness-priority-low | Low | Nice to have, address when convenient |
If the user does not express a preference, default to Low.
The user-facing question is the same regardless of issue tracker. The internal mapping differs by platform and is applied during submission (Step 5).
Deferred Label Check:
Check if Arness labels exist by running gh label list --search "arness-". If fewer than 7 Arness labels are found, create the missing ones using gh label create --force for each label per ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-init/references/platform-labels.md. This is idempotent and safe to run on every invocation.
Create the issue using the GitHub CLI:
gh issue create --title "<title>" --body "<body>" --label "<type-label>,<priority-label>"
Report to the user:
gh issue create)/arn-code-pick-issue later to pick this up for implementation, or continue with your current work."Use the Atlassian MCP server to create a Jira issue:
<Jira project from ## Arness config><title><body> (in Jira-compatible markdown)[arness-<type-label>, arness-priority-<level>]Report to the user:
https://<jira-site>/browse/<issue-key>/arn-code-pick-issue later to pick this up for implementation, or continue with your current work."none — Inform the user that issue management is not configured. Suggest running /arn-planning to get started./arn-planning to get started.gh CLI not authenticated — Suggest running gh auth login to authenticate./mcp to check status or /arn-planning to reconfigure.## Arness config is correct. Suggest running /arn-planning to reconfigure.${CLAUDE_PLUGIN_ROOT} for all paths referencing plugin files./arn-code:skill-name prefix (e.g., /arn-code-init, /arn-code-pick-issue).