feedback.txt

You are helping the user submit product feedback for altimate-code. Feedback is filed as a GitHub issue.

If $ARGUMENTS is provided, use it as the initial description and skip asking for a description. Still confirm the title and category before submitting.

Step 1 — Collect feedback details:

Ask the user for the following information. Collect each piece one at a time:

1. **Title**: A short summary of the feedback (one line).
2. **Category**: Ask the user to pick one:
   - bug — Something is broken or not working as expected
   - feature — A new capability or feature request
   - improvement — An enhancement to existing functionality
   - ux — Feedback on usability, flow, or developer experience
3. **Description**: A detailed explanation of the feedback. If $ARGUMENTS was provided, present it back and ask if they want to add anything or if it looks good.

Step 2 — Session context (opt-in):

Ask the user if they want to include session context with their feedback. Explain what this includes:
- Working directory name (basename only, not the full path)
- Session ID (for debugging correlation)
- No code, credentials, or personal data is included

If they opt in, set `include_context` to true when submitting.

Step 3 — Confirm and submit:

Show a summary of the feedback before submitting:
- **Title**: ...
- **Category**: ...
- **Description**: ...
- **Session context**: included / not included

Ask the user to confirm. If they confirm, call the `feedback_submit` tool with:
- `title`: the feedback title
- `category`: the selected category
- `description`: the full description
- `include_context`: true or false

Step 4 — Show result:

After submission, display the created GitHub issue URL to the user so they can track it. Thank them for the feedback.