使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-catchup開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
ds-catchup
Bring the user back up to speed in a minute, and hand them every call only they can make.
Steps
- Keep this turn read-only. Do not change code, start jobs or post anything.
- Collect what happened since the user's last message: your own work, subagent reports, and messages from others. Tool notifications are not user messages.
- 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.
- 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.
- 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.
- 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.
