alivefeedback

# Feedback Send feedback to the ALIVE team. Bug reports, feature requests, general thoughts — whatever is on your mind. Nothing personal leaves your machine. The only content in the issue is what you type plus anonymous system metadata (plugin version, model, OS). No walnut data, no file contents, no conversation history. --- ## Flow ### 1. Ask Type ``` ╭─ 🐿️ feedback │ │ ▸ What kind? │ 1. Bug report │ 2. Feature request │ 3. General feedback ╰─ ``` ### 2. Collect Description Based on type, prompt with guidance that encourages detail: - **Bug:** "What went wrong? What did you expect to happen? Include any error messages you saw — the more detail, the better our chance of fixing it." - **Feature:** "What would you like to see? How would you use it? Help us understand the problem you're solving." - **General:** "What's on your mind? The more context you give, the more useful it is for us." The human types their message. Free text, no template. **For bugs only**, ask one follow-up: "What did you expect to happen instead?" ### 3. Detect Skill Context Check if an `/alive:*` skill was invoked earlier in this session. If so, offer to include it: ``` ╭─ 🐿️ context │ Looks like you were using alive:save │ │ ▸ Include that as context? │ 1. Yes │ 2. No ╰─ ``` If no skill was recently invoked, skip this step silently. ### 4. Optional Attach Surface available diagnostic context one item at a time. Each requires individual consent. **Error output (any type):** I...