本文へ移動
cccskills
無料GitHub で公開

catchup

Rebuilds session context after a clear by reading git history, plans, and beads state. Triggers on 'catch up'.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.4 KB
  • evals/evals.json2.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Context Recovery Skill

You are resuming work after a session clear. Your job is to rebuild full working context from git history, the latest plan, and beads issue state, then produce a visible briefing and internalize everything needed to continue.

Step 1: Branch Check

If not on main, store the merge-base SHA and continue.

Run these commands:

git branch --show-current
git merge-base HEAD main 2>/dev/null

Step 2: Git History

If on main (no merge-base range), use the last ~20 commits:

git log --oneline -20
git diff --stat HEAD~20..HEAD
git diff --stat          # uncommitted changes
git diff --cached --stat # staged changes

If on a feature branch, use the merge-base range:

git log --oneline <merge-base>..HEAD
git diff --stat <merge-base>..HEAD
git diff --stat          # uncommitted changes
git diff --cached --stat # staged changes

Then read every file that appears in the diff stats (both committed and uncommitted). Build a mental model of what changed and why.

Step 3: Latest Plan

Find the most recently modified file in ~/.claude/plans/:

ls -t ~/.claude/plans/ | head -1

Read that file in full. Only include the Active Plan section in the briefing if the plan is relevant to the current repository (e.g., references the same project, codebase, or directory). Skip it if the plan is for a different project.

Step 4: Beads State

Run these commands (skip if bd is not available):

bd list --status=in_progress
bd ready

Note which issues are actively being worked and which are unblocked and available.

Step 5: Produce Briefing

Output a concise visible briefing in this format:

## Catchup Briefing

**Branch:** <branch-name> (<N> commits ahead of main)

### Recent Changes
- <1-line summary per commit, grouped by theme>

### Uncommitted Work
- <files with uncommitted/staged changes, or "Clean working tree">

### Active Plan
- <plan title + key status from the plan file>

### Beads Status
- **In Progress:** <issue titles>
- **Ready:** <issue titles>

### Suggested Next Step
> <concrete next action based on plan state + beads + uncommitted work>

After outputting the briefing, you now have full context. Continue working as if you never lost the session.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

日本語の概要は準備中です。原文の説明を表示しています。

SDiamante13/dotfiles82026年10月2日 更新

changelog

無料

Generate a bullet-point summary of branch changes for a PR description. Triggers on "changelog", "pr summary", "summarize branch", or "/changelog".

日本語の概要は準備中です。原文の説明を表示しています。

SDiamante13/dotfiles82026年10月2日 更新

commit

無料

Commit the current changes with quality checks, status review, staged diff inspection, appropriate tests, and a clear commit message. Use when the user says "commit", "c", asks to make a commit, or wants changes saved in git.

日本語の概要は準備中です。原文の説明を表示しています。

SDiamante13/dotfiles82026年10月2日 更新

declutter

無料

Refactor code to remove dead code, useless comments, unused variables, and unused imports. Use when asked to declutter a class, clean up noisy code, remove cruft, or run `/refactor:declutter`.

日本語の概要は準備中です。原文の説明を表示しています。

SDiamante13/dotfiles82026年10月2日 更新

dry

無料

Refactor duplicated code by extracting helpers, shared abstractions, or clearer reusable structure. Use when asked to apply DRY, remove duplication, consolidate repeated logic, or run `/refactor:dry`.

日本語の概要は準備中です。原文の説明を表示しています。

SDiamante13/dotfiles82026年10月2日 更新

Build a rich, self-contained HTML explanation of a code change — diff, branch, commit range, MR/PR — with background, intuition, a code walkthrough, diagrams, and a glossary, then quiz the reader interactively in chat. Use when the user asks to explain a change, understand a PR/MR, walk through a diff, onboard onto a branch, or says "explain this PR", "what does this branch do", "teach me this change", or "/explain-diff".

日本語の概要は準備中です。原文の説明を表示しています。

SDiamante13/dotfiles82026年10月2日 更新

SDiamante13 のスキルをすべて見る

このスキルの問題を報告する