skills.rest
vieko
viekoCOMMUNITY
Explore all skills by this author →
Website𝕏@viekoGitHub

session-context

Read session context from .sessions/index.md to assemble project status and decisions.

3|Updated Nov 18, 2025
Search Tags:#automation#architecture#blockers#claude-code#context-reading#project-history#session-context
One-click install
npx skills add https://github.com/vieko/create-sessions-dir --skill session-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-context
Source: https://github.com/vieko/create-sessions-dir/tree/main/templates/claude/skills/session-context
Command: npx skills add https://github.com/vieko/create-sessions-dir --skill session-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Claude read project context from .sessions/index.md to inform decisions without relying on memory, reducing context-switching and rework.

Core Features & Use Cases

  • Read .sessions/index.md to derive project status, decisions, blockers
  • Reference plans, docs, and package context for deeper understanding
  • Works for monorepos with .sessions/packages context
  • Use Case: Quickly answer "What is the current status?" or "What decisions were made recently?"

Quick Start

Ask Claude about the current project context; the Skill will read .sessions/index.md to provide an informed answer.

Frequently Asked Questions about session-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read project context from session notes instead of relying on memory?▼

Session context reads .sessions/index.md to automatically retrieve your project's current status, recent decisions, and blockers without manual recap. This eliminates context-switching and reduces rework when returning to ongoing work.

What should I store in .sessions/index.md to track project decisions and blockers?▼

Document your project status, architectural decisions, known blockers, and work history in .sessions/index.md. The Skill reads this file to assemble a current context snapshot and answer questions about what was decided or what's blocking progress.

Can session context work with monorepos and package-specific information?▼

Yes, session context supports monorepos by reading .sessions/packages/ alongside .sessions/index.md. This lets you maintain and retrieve context for individual packages within a larger repository.

How do I quickly answer 'what is the current project status' without manual investigation?▼

Ask Claude about the project status or recent decisions. The Skill automatically reads .sessions/index.md, .sessions/plans/, and .sessions/docs/ to provide an informed answer based on your living session notes.

What's the difference between storing context in .sessions/index.md versus keeping it in code comments?▼

Session context in .sessions/index.md is structured, version-controlled, and automatically retrieved by the Skill when needed, whereas code comments scatter context across files and require manual search. Centralized session notes enable faster, more reliable context retrieval.

Related Skills

Explore More Software Engineering Skills→
abnegateabnegate
2

history

Searches local .jsonl session files for keywords and emits resume commands for matching conversations.

Community
Basic
thechandanbhagatthechandanbhagat
8

docs

Generate Markdown documentation from codebases for CI pipelines.

Community
Intermediate
a53alia53ali

architecture-decision-record

Write, update, and query Architecture Decision Records using Markdown templates.

Community
Intermediate
TaylorHustonTaylorHuston
69

debrief

Extract memories from end-of-session conversations and update profile files.

Community
Intermediate