name: itx:bug-new

Bug Report Creation

Create a GitHub issue for a bug based on the current conversation context.

Instructions

1. Analyze Context: Review the current conversation for:

   • Error messages and stack traces
   • Unexpected behavior descriptions
   • Steps that led to the issue
   • Environment details (version, OS, etc.)

2. Ask for Customer Outcome: Use AskUserQuestion to ask:

   "What should the user be able to do when this bug is fixed?"

   Example outcomes:

   • "User can install dependencies without version mismatch errors"
   • "User can add resources with special characters in names"
   • "User can run status command without timeout"

3. Form Issue Title: Use the customer outcome as the issue title.

   • Format: <outcome> (what the user can do after fix)
   • Example: "User can install dependencies without version mismatch errors"
   • The user can change this later if needed

4. Gather Details:

   • If the user provided a description argument, use it for context
   • Identify steps to reproduce if available
   • Note environment details

5. Load Project Name (for environment section):

   bash
   1ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json"
   2if [ -f "$ITX_CONFIG" ]; then
   3  PROJECT_NAME=$(jq -r '.project.name // ""' "$ITX_CONFIG")
   4  VERSION_LABEL=$(jq -r '.project.version_label // "Version"' "$ITX_CONFIG")
   5fi
   6
   7# Fallback: use repository name if no config
   8if [ -z "$PROJECT_NAME" ]; then
   9  REMOTE_URL=$(git config --get remote.origin.url)
   10  PROJECT_NAME=$(echo "$REMOTE_URL" | sed -E 's/.*[:/]([^/]+\/[^/]+)(\.git)?$/\1/' | cut -d'/' -f2)
   11fi

6. Create Issue: Use gh issue create with:

   bash
   1gh issue create \
   2  --title "<customer outcome from step 3>" \
   3  --label "bug" \
   4  --label "needs-triage" \
   5  --body "<structured bug report>"

7. Bug Report Body Format:

   markdown
   1## Customer Outcome
   2<The outcome statement - what user can do when fixed>
   3
   4## Description
   5<What is currently happening / the bug>
   6
   7## Steps to Reproduce
   81. <step>
   92. <step>
   10
   11## Expected Behavior
   12<What should happen>
   13
   14## Actual Behavior
   15<What actually happens>
   16
   17## Environment
   18- <project name> version: <version>
   19- Platform: <os/platform>
   20- Other relevant details: <details>
   21
   22---
   23
   24<details>
   25<summary>Prompt Log</summary>
   26
   27**Stage**: bug-creation
   28**Skill**: /itx:bug-new
   29**Timestamp**: <ISO timestamp>
   30**Model**: <model>
   31
   32```prompt
   33<original user prompt/context that led to this bug>

   </details> ```

8. Return: The issue URL and number

Notes

• Always ask for customer outcome before creating the issue
• The outcome becomes the title - focus on what the user gains
• Always add needs-triage label for new bugs
• Include as much context as available from the conversation
• If steps to reproduce are unclear, note that in the issue
• Project name dynamically detected or loaded from config

Prompt Logging

REQUIRED: After creating the issue, append prompt log to .itx/<N>/00_PLAN.md.

See AGENTS.md for format specification.

bash
1mkdir -p .itx/<issue-number>
2# Append prompt log to .itx/<issue-number>/00_PLAN.md