ds-catchup — Claude Code skill: what it does, how to install
ds-catchup — a skill for Claude Code summarizes changes since the last message and lists decisions awaiting the user's input. It runs when someone returns after a long pause or asks what happened.
MIT 540 installs ★ 320 updated 2026-10-28
npx skills add aicodeking/deepseek-stack --skill ds-catchup -a claude-codeWhat ds-catchup does
ds-catchup gathers work since the user's previous message, including agent activity, subagent reports, and messages from other people. It then checks the current state of affected tests, branches, PRs, and running jobs using fresh command output. The turn is read-only: the skill does not edit code, launch jobs, or post messages.
The update stays under 100 words and explains what changed. It then lists decisions only the user can make, with the impact, supporting evidence, risk, and a recommendation for each. Missing facts are marked as unknown. If no decisions are waiting, the skill says so plainly and stops without taking further action.
What it helps with
- catch up on work since the previous message
- check the latest state of tests and branches after an unattended run
- identify choices or approvals waiting for the user
- separate user decisions from tasks the agent can handle
Example prompts for the agent
- Summarize what changed since my last message and list the decisions waiting for me.
- I’m back after a long run. What happened, and what needs my decision?
- /ds-catchup
How to install ds-catchup
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-catchup -a claude-code2Manually: put the files in place
~/.claude/skills/ds-catchup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ds-catchup/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-catchup -a codex2Manually: put the files in place
.agents/skills/ds-catchup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-catchup -a cursor2Manually: put the files in place
.cursor/skills/ds-catchup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aicodeking/deepseek-stack skills/ds-catchup2Manually: put the files in place
.github/skills/ds-catchup/SKILL.md1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-catchup -a gemini-cli2Platform CLI
gemini skills install https://github.com/aicodeking/deepseek-stack --path skills/ds-catchupManually: put the files in place
.devin/skills/ds-catchup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-catchup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ds-catchup
How do I install ds-catchup in Claude Code?
Run npx skills add aicodeking/deepseek-stack --skill ds-catchup -a claude-code.
What does ds-catchup do?
It gives a short update on activity since the user's last message, then lists open decisions with evidence, risks, and recommendations.
Does ds-catchup change code or start jobs?
No. It keeps the catch-up turn read-only and does not launch new jobs.
Source text
SKILL.md · MIT
--- name: ds-catchup description: "Give the user a short plain-language catch-up on what changed since their last message, followed by every decision still waiting on them. Use when the user returns after a long or unattended run, asks 'where are we', 'what did I miss', or types /ds-catchup." --- # ds-catchup Bring the user back up to speed in a minute, and hand them every call only they can make. ## Steps 1. Keep this turn read-only. Do not change code, start jobs or post anything. 2. Collect what happened since the user's last message: your own work, subagent reports, and messages from others. Tool notifications are not user messages. 3. Check the current state of anything touched: tests, branches, PRs, running jobs. Use fresh command output, not memory. Fix any number that does not match the source and say you fixed it. 4. Write what changed in under 100 words. Say what it means for the user, for example "the login bug is fixed and its test passes". Leave out hashes, paths and commands unless the user needs one to act. 5. List decisions waiting on the user. A decision is something only they can do: a product choice, an approval, an irreversible action, or access you lack. Include old ones still open. For each give: what it changes, the evidence, the risk, your recommendation, and "unknown" for missing facts. 6. If nothing waits on them, say so plainly. ## Stop when - The catch-up and the decision list are written. One reply, no follow-up work. ## Rules - Never invent a decision to fill the list. - Work you can still do yourself is not a decision for the user. - Name things the way the user would, not by internal labels. - Short sentences, no jargon.
© aicodeking · MIT · aicodeking/deepseek-stack