skills.rest
yousufjoyian
yousufjoyianCOMMUNITY
Explore all skills by this author →
GitHub

context-extract

Append timestamped session context to HISTORY.md, DECISIONS.md, and DIRECTIONS.md files.

Updated Aug 23, 2026
Search Tags:#documentation#context#CLAUDE#append-only#session-history#project-logging
One-click install
npx skills add https://github.com/yousufjoyian/claude-skills --skill context-extract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-extract
Source: https://github.com/yousufjoyian/claude-skills/tree/main/context-extract
Command: npx skills add https://github.com/yousufjoyian/claude-skills --skill context-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Append conversation context to the cumulative project history without overwriting existing records, enabling durable, audit-friendly memory across CLAUDE sessions.

Core Features & Use Cases

  • Append-only logging for HISTORY.md, DECISIONS.md, and DIRECTIONS.md to preserve the full decision trail.
  • Reads existing context, timestamps new sessions, and maintains a clean archive structure for old entries.
  • Use Case: You run multiple sessions on a project and want a complete, reconstructible history for onboarding, audits, or review.

Quick Start

Use the context-extract skill to append your current session to the project's .claude/context directory.

Frequently Asked Questions about context-extract

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

FAQPage Schema
How do I maintain a complete project history across multiple Claude sessions?▼

Append-only logging preserves your full decision trail by timestamping each session and adding it to HISTORY.md, DECISIONS.md, and DIRECTIONS.md without overwriting prior entries. This creates an auditable, reconstructible record across all Claude sessions on a project.

What's the best way to keep session context organized without losing previous notes?▼

Use an append-only workflow that reads your current context files, adds a timestamped session block, and archives older content separately. This approach ensures nothing is lost while keeping active context clean and retrievable.

Can I automatically log Claude conversation context to my project documentation?▼

Yes. The skill appends your current session context to designated markdown files in the .claude/context directory, building cumulative logs that persist across project work without manual entry or file overwrites.

Why should I use an append-only archive instead of updating a single context file?▼

Append-only logging prevents data loss and enables audits by retaining the complete decision trail. Each timestamped entry remains intact, allowing you to review how your project evolved and reconstruct reasoning from any prior session.

Do I need any dependencies or setup to start logging Claude session context?▼

No external dependencies are required. The skill reads and appends to markdown files in your .claude/context directory, making it lightweight and compatible with any Claude workflow that produces session notes.

Related Skills

Explore More Content & Communication Skills→
arjunrattan-lab-aiarjunrattan-lab-ai

session-recap

Generate a session summary and log to a Markdown file.

Community
Intermediate
whjelmarwhjelmar

Memory Review

Review session history, decisions, and project progress over time.

Community
Intermediate
ThiagoVitaleThiagoVitale

gsd-complete-milestone

Archive completed milestones and update project documentation for the next version.

Community
Advanced
bolivian-perubolivian-peru
113

generation-timeline

Correlate NixOS generation changes with application failures and audit logs.

Community
Advanced