사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-catchup시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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.
