read-continue-here
정보
이 Claude Skill은 코딩 세션 시작 시 CONTINUE_HERE.md 파일을 자동으로 읽어 이전 작업을 재개하며, 감지, 구문 분석, 정리 과정을 처리합니다. 중단 후 세션 연속성을 위해 설계되었으며 수동으로 또는 SessionStart 훅을 통해 트리거될 수 있습니다. 개발자들은 이를 통해 컨텍스트를 신속하게 구성하고 세션 간 자동화된 워크플로우 전환을 설정합니다.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/read-continue-hereClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Read Continue Here
Read structured continuation file → resume work from prev session.
Use When
- New session + CONTINUE_HERE.md in project root
- SessionStart hook injects continuation ctx
- Bootstrap identity → detect prior session artifacts
- Set up auto-continuation detect (one-time infra)
In
- Required: Project dir (default cwd)
- Optional: Configure infra? (hook + CLAUDE.md instr)
- Optional: Delete after consume? (default yes)
Do
Step 1: Detect + Read
Check for CONTINUE_HERE.md in project root:
ls -la CONTINUE_HERE.md 2>/dev/null
Absent → exit graceful, nothing to continue.
Present → read. Parse 5 sections: Objective, Completed, In Progress, Next Steps, Context. Extract timestamp + branch from header.
→ File read, sections parsed → clear mental model of prev session state.
If err: malformed (missing sections, empty) → partial signal, extract what's there, note gaps to user.
Step 2: Freshness
Compare file timestamp vs now:
# File modification time
stat -c '%Y' CONTINUE_HERE.md 2>/dev/null || stat -f '%m' CONTINUE_HERE.md
# Current time
date +%s
Classify:
- Fresh (< 24h, same branch) → act direct
- Stale (> 24h or diff branch) → flag user
- Superseded (new commits after handoff) → someone worked since handoff
Branch check:
git branch --show-current
git log --oneline --since="$(stat -c '%Y' CONTINUE_HERE.md | xargs -I{} date -d @{} --iso-8601=seconds)" 2>/dev/null
→ Freshness classification + evidence.
If err: no git repo → skip branch/commit checks. Use timestamp from file header.
Step 3: Summarize + Confirm
Present state concise:
- "Prev objective: [Objective]"
- "Done: [summary]"
- "In progress: [summary]"
- "Proposed next: [Next Steps 1]"
Stale/superseded → present evidence, ask proceed or fresh.
Next Steps tagged **[USER]** → surface explicit, need user decisions first.
→ User confirms plan, maybe adjust. Clear mandate next.
If err: user says "fresh" or "ignore file" → ack, proceed w/o ctx. Offer delete file → no future confusion.
Step 4: Act
Begin Next Steps 1 (or where user directed):
- Reference In Progress → partial state
- Use Context → avoid retry failed approaches
- Trust Completed = done, no re-verify unless asked
→ Agent productive on right task, informed by file.
If err: ambiguous Next Steps or unclear In Progress → ask user, no guess.
Step 5: Clean Up
After handoff consumed + work underway → delete CONTINUE_HERE.md:
rm CONTINUE_HERE.md
Stale files → confusion future sessions.
→ File gone. Root clean.
If err: user wants keep (e.g. ref during session) → leave but note delete before session end → prevent re-consume.
Step 6: SessionStart Hook (Optional)
Set up auto-read CONTINUE_HERE.md at session start.
Create hook:
mkdir -p ~/.claude/hooks/continue-here
cat > ~/.claude/hooks/continue-here/read-continuation.sh << 'SCRIPT'
#!/bin/bash
# SessionStart hook: inject CONTINUE_HERE.md into session context
# OS-aware: works on native Linux, WSL, macOS, and Windows (Git Bash/MSYS)
set -uo pipefail
# --- Platform detection ---
detect_platform() {
case "$(uname -s)" in
Darwin) echo "mac" ;;
Linux)
if grep -qi microsoft /proc/version 2>/dev/null; then
echo "wsl"
else
echo "linux"
fi ;;
MINGW*|MSYS*|CYGWIN*) echo "windows" ;;
*) echo "unknown" ;;
esac
}
PLATFORM=${PLATFORM:-$(detect_platform)}
CONTINUE_FILE="$PWD/CONTINUE_HERE.md"
if [ ! -f "$CONTINUE_FILE" ]; then
exit 0
fi
# Strip CRLF (files on NTFS often have Windows line endings)
CONTENT=$(sed 's/\r$//' "$CONTINUE_FILE")
# JSON-escape: prefer jq, fall back to portable awk
if command -v jq >/dev/null 2>&1; then
ESCAPED=$(printf '%s' "$CONTENT" | jq -Rsa .)
else
ESCAPED=$(printf '%s' "$CONTENT" | awk '
BEGIN { ORS=""; print "\"" }
{
gsub(/\\/, "\\\\")
gsub(/"/, "\\\"")
gsub(/\t/, "\\t")
if (NR > 1) print "\\n"
print
}
END { print "\"" }
')
fi
cat << EOF
{"hookSpecificOutput":{"sessionStartContext":{"additionalContext":$ESCAPED}}}
EOF
SCRIPT
chmod +x ~/.claude/hooks/continue-here/read-continuation.sh
Add to ~/.claude/settings.json SessionStart hooks array:
{
"type": "command",
"command": "~/.claude/hooks/continue-here/read-continuation.sh",
"timeout": 5
}
→ Hook script exists, executable, registered. Next session start → CONTINUE_HERE.md content injected into ctx.
If err: invalid JSON after edit → check settings.json. Test hook: cd /your/project && ~/.claude/hooks/continue-here/read-continuation.sh. Falls back to awk if no jq → jq rec but optional.
Step 7: CLAUDE.md Instr (Optional)
Add brief instr to project CLAUDE.md → Claude understands file purpose:
## Session Continuity
If `CONTINUE_HERE.md` exists in the project root, read it at session start. It contains a structured handoff from a prior session: objective, completed work, in-progress state, next steps, and context. Act on it — acknowledge the continuation, summarize prior state, and propose resuming from the Next Steps section. If the file is older than 24 hours, flag this to the user before proceeding. After the handoff is consumed, the file can be deleted.
→ CLAUDE.md has instr. Future sessions read + act on CONTINUE_HERE.md even if no hook.
If err: no CLAUDE.md → create w/ just this section. Too long → add near top, not truncated.
Check
- CONTINUE_HERE.md detected (or absence handled)
- Freshness assessed (timestamp, branch, commits)
- Plan presented + confirmed by user
- Work began from correct Next Steps
- File cleaned up after consume
- (Optional) Hook script exists + executable
- (Optional) CLAUDE.md has continuity instr
Traps
- Act w/o confirm: Always present plan. User may have changed mind, even if fresh.
- Trust stale blind: > 24h or diff branch = suggestion not mandate. Check freshness.
- Skip Context: Most valuable = failed approaches. Skip → retry dead ends.
- Forget clean up: Leftover file → next session re-acts on it.
- Re-verify Completed: Don't redo done work unless asked. Trust prev assessment.
→
write-continue-here— complement: write file at session endbootstrap-agent-identity— full identity reconstruct, includes continuation detectmanage-memory— durable cross-session knowledgewrite-claude-md— project instr where continuity guidance lives
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
