`/note-context`

Session Context

Creates a pinned blue note with project state: current branch, uncommitted changes, key files being worked on (3-5 with annotations), decisions made, open questions, and a mandatory "Resume With" section that tells the next session exactly what to do.

Quick Example

Claude Code

/note-context /note-context

Auto-captures git state, recent decisions, and generates resume instructions.

Screenshot Placeholder

Result: Session Context sticky note (blue color) created from the command above

Key Features

📎

Key Files List

3-5 most important files with 5-word annotations. Quick orientation for the next session.

🌿

Git State Snapshot

Branch, uncommitted changes summary, loop progress — everything a new session needs to know.

▶️

Resume Instructions

Mandatory "Resume With" section. Must be specific enough that reading ONLY this section tells you what to do.

❓

Open Questions

Unresolved items from the session. Prevents knowledge loss between sessions.

Real-World Examples

End of day

/note-context /note-context

Auto-captures git state, recent decisions, and generates resume instructions.

With notes

/note-context Paused mid-refactor, auth.ts needs the refresh token flow

Your context added to auto-generated state for richer handoff.

Non-git project

/note-context Working on design docs in Figma

Works without git repo. Captures note state and provided context.

The Handoff Problem

When you start a new Claude Code session, all context is lost. You need to re-explain what you were working on, which files matter, and what’s left to do.

/note-context solves this by creating a pinned blue note with everything the next session needs.

Output Sections

Section	Content
Header	`project @ branch \| N uncommitted changes`
Working On	Current task, specific and clear
Key Files	3-5 most important files with 5-word annotations
State	Branch purpose, uncommitted summary, loop progress
Key Decisions	Decisions made this session only
Open Questions	Unresolved items and unknowns
Resume With	Exact instructions for the next session

Key Files Format

Each file gets a short annotation:

src/auth.ts — JWT validation middleware (refactoring)
src/api/users.ts — New endpoint, needs tests
tests/auth.test.ts — 3 tests failing on refresh

Maximum 5 files. Only the most relevant ones.

The “Resume With” Section

This is the critical section. Quality bar:

Reading ONLY “Resume With” should tell a fresh session exactly what to do next.

Good:

Resume With: Fix the refresh token flow in src/auth.ts:45.
The validateToken function needs to check token expiry
and call refreshToken() before returning 401.
Run tests with: npm test -- auth

Bad: