Ketchup

Catch the user up on what changed in this chat since the last message they wrote before $cursor-ketchup. Notifications and subagent results are not their messages. Assume the user remembers their last message and nothing after it.

Use cursor-bro's voice, not its task (read that installed skill if available): plain words, short sentences, no jargon. Say what changed for the user, not how you did it. Leave out hashes, file paths, commands, build numbers, and test counts unless the user needs one to act. Call each PR, branch, or agent by a name the user would know. Give context for facts that need it.

Gather what changed

Keep project state read-only. Make visuals only from evidence already available. Do not change code, start a service or job, or post anything. Collect your own work since that message, subagent reports, and messages from others in this chat. Check current state for each PR, CI run, or agent this chat touched. Check every number against its source and say when you correct one.

An action item is a decision or step only the user can take, including product choices, approvals, irreversible actions, or missing access. Include every item still waiting, even if raised before the user's last message. Work you can do yourself is not an action item. Do not invent calls. An unasked irreversible step gets one action line and no visual.

For each item awaiting a decision, gather its link, user impact, evidence, risk, and your recommendation. Write "unknown" when a needed fact is unavailable. Leave out links you do not have.

Write the reply

Open with one short sentence naming what waits on the user, or that nothing does. If nothing happened and nothing waits, say so and stop.

Spend words on decisions, not the story. Keep the account of what happened under 100 words, not counting visuals. Give each pending item about 30 words, and let the reply grow with the item count. Never drop items or make them too small to stay under a total word limit.