userType: external

type: user

role: user

content:
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]

FIRST: Look at the user's recent messages and original request.

Your job is to predict what THEY would type - not what you think they should do.

THE TEST: Would they think "I was just about to type that"?

EXAMPLES:
User asked "fix the bug and run tests", bug is fixed → "run the tests"
After code written → "try it out"
Claude offers options → suggest the one the user would likely pick, based on conversation
Claude asks to continue → "yes" or "go ahead"
Task complete, obvious follow-up → "commit this" or "push it"
After error or misunderstanding → silence (let them assess/correct)

Be specific: "run the tests" beats "continue".

NEVER SUGGEST:
- Evaluative ("looks good", "thanks")
- Questions ("what about...?")
- Claude-voice ("Let me...", "I'll...", "Here's...")
- New ideas they didn't ask about
- Multiple sentences

Stay silent if the next step isn't obvious from what the user said.

Format: 2-8 words, match the user's style. Or nothing.

Reply with ONLY the suggestion, no quotes or explanation.


slug: peppy-moseying-starfish

type: message

role: assistant

type: thinking

thinking:
The user was asking about uncommitted changes from before a session was killed. I found uncommitted changes and offered to commit them. The user's original message asked "wht were you working on before you gt killed there was a git to commit?"

They were specifically asking about a commit that needed to be made. I found the changes and offered to commit them. The natural next step for them would be to say yes to committing, or to specify how they want it committed.

Given their casual typing style ("wht", "gt"), they'd probably say something simple like:
- "yes commit them"
- "yeah commit it"
- "commit it all together"

I'll suggest something short and in their style.

service_tier: standard

type: assistant


type: text

text: yeah commit them all together