メニュー
Report a bug, request a feature, or send general feedback to the ALIVE team. Collects safe system metadata, shows a preview, and creates a GitHub Issue. Nothing personal leaves the machine, only what you type and anonymous system info.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | alive:feedback |
| description | Report a bug, request a feature, or send general feedback to the ALIVE team. Collects safe system metadata, shows a preview, and creates a GitHub Issue. Nothing personal leaves the machine, only what you type and anonymous system info. |
| user-invocable | true |
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.
╭─ 🐿️ feedback
│
│ ▸ What kind?
│ 1. Bug report
│ 2. Feature request
│ 3. General feedback
╰─
Based on type, prompt with guidance that encourages detail:
The human types their message. Free text, no template.
For bugs only, ask one follow-up: "What did you expect to happen instead?"
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.
Surface available diagnostic context one item at a time. Each requires individual consent.
Error output (any type): If recent tool errors or hook failures occurred in this session, offer regardless of feedback type:
╭─ 🐿️ diagnostics
│ There were errors earlier in this session.
│
│ ▸ Include the error output? (helps us diagnose)
│ 1. Yes, include it
│ 2. No, skip
╰─
Walnut name (bugs only): If a walnut is loaded and the type is bug, offer:
╭─ 🐿️ diagnostics
│ You're working in a walnut right now.
│
│ ▸ Include the walnut name? (just the name, nothing else)
│ 1. Yes
│ 2. No
╰─
If no errors occurred in the session and the type isn't a bug, skip this step entirely.
Gather these automatically — no user interaction needed:
| Field | How to get it |
|---|---|
| Plugin version | Read ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json → version field. Fallback: use CLAUDE.md frontmatter version. |
| Engine/model | You know which model you are — state it (e.g., claude-opus-4-7) |
| OS/platform | Run: uname -s via Bash |
| Context usage % | Read .alive/.context_pct if it exists (written by statusline). Otherwise: "unavailable" |
| Session duration | Read .alive/.session_id (written by statusline). Then open .alive/_squirrels/{session_id}.yaml and calculate minutes elapsed from its started: field to now. Do not guess the session ID from directory contents — if .session_id is missing, report "unavailable". |
Never collect: walnut contents, file paths, conversation history, PII, credentials, .alive/key.md.
Show the complete issue in a bordered block. This is exactly what will be posted — nothing hidden.
╭─ 🐿️ feedback preview
│
│ Title: [Bug] Save skill dropped stash items
│
│ Body:
│ ### Description
│ [their message]
│
│ ### Expected Behaviour
│ [their answer — bug only]
│
│ ### Context
│ - Skill: alive:save
│ - Error output: [if opted in]
│ - Walnut: [name, if opted in]
│
│ ### System
│ - Plugin: 3.0.0
│ - Engine: claude-opus-4-7
│ - OS: Darwin
│ - Context: 45%
│ - Session: ~32min
│
│ Labels: feedback, bug
│
│ → this will be posted publicly to github.com/alivecontext/alive
│
│ ▸ Send?
│ 1. Send
│ 2. Edit description
│ 3. Cancel
╰─
Title format: [Bug] first ~60 chars of description / [Feature] ... / [Feedback] .... Keep under 70 chars total.
If the human picks "Edit" — ask what they want to change, update the preview, show it again.
First, verify gh is available:
which gh >/dev/null 2>&1 && gh auth status >/dev/null 2>&1
If either check fails, skip straight to the fallback in Step 8.
If gh is ready, create the issue. Use a heredoc for the body to handle multiline content and special characters:
gh issue create \
--repo alivecontext/alive \
--title "[Bug] Save skill dropped stash items" \
--label "feedback,bug" \
--body "$(cat <<'ALIVE_FEEDBACK_EOF'
### Description
The save skill lost 3 of my stash items during checkpoint...
### Expected Behaviour
All stash items should persist through save...
### Context
- Skill: alive:save
### System
- Plugin: 3.0.0
- Engine: claude-opus-4-7
- OS: Darwin
- Context: 45%
- Session: ~32min
---
*Sent via `/alive:feedback`*
ALIVE_FEEDBACK_EOF
)"
Label mapping:
--label "feedback,bug"--label "feedback,enhancement"--label "feedback"On success (gh returns a URL):
╭─ 🐿️ sent
│ Feedback submitted: https://github.com/alivecontext/alive/issues/42
│ Thanks — back to work.
╰─
On failure (gh not installed, not authenticated, or network error):
╭─ 🐿️ couldn't send
│ [error message]
│
│ Two options:
│ 1. Run `gh auth login` in your terminal, then try /alive:feedback again
│ 2. Copy the issue below and paste it at:
│ github.com/alivecontext/alive/issues/new
│
│ ---
│ [show the full formatted issue body for copy-paste]
╰─
These are non-negotiable. The skill MUST NOT:
.alive/key.md or world identityThe walnut name is the only walnut-related data that CAN be included, and only with explicit per-item consent for bug reports.
The squirrel can suggest /alive:feedback when it notices problems — but only if feedback_nudges is enabled in .alive/preferences.yaml (default: true).
When to nudge:
How to nudge:
╭─ 🐿️ that hook failed
│ Want to report it? /alive:feedback
╰─
Frequency cap: Maximum one nudge per session. If you've already nudged once this session, don't show another.
This is a squirrel instinct, not a hook. The squirrel notices errors as part of its always-watching behaviour and surfaces the nudge when feedback_nudges is on.
Morning briefing -- read all walnut states, surface priorities, inbox count, stale walnuts, people nudges
Morning operating system -- sync inputs, read everything, surface priorities, show the day
Load an ALIVE walnut -- read kernel files, show current state, surface one observation, ask what to work on
Checkpoint -- route stash items, write log entry, update bundle, trigger projection, reset stash
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.