update-context

Append timestamped notes and update state.json and manifest for active sessions.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/nexus-a1/claude-skills --skill update-context-nexus-a1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-context
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/update-context
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill update-context-nexus-a1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Annotate an active work session with notes, scope changes, or new findings and ensure they are preserved in a timestamped entry.

Core Features & Use Cases

  • Append timestamped notes to the session's state.json without altering lifecycle state
  • Update the manifest with the latest update time for quick session retrieval
  • Record mid-session discoveries, blockers, decisions, and scope changes for traceability
  • Non-destructive: integrates into the existing state.json without overwriting existing data

Quick Start

Record a note for an active session by providing the identifier and a brief observation.

Frequently Asked Questions about update-context

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

FAQPage Schema
How do I log mid-session notes and updates to state.json?

You can log mid-session notes by appending timestamped entries to the state.json updates array, which records discoveries, scope changes, and decisions while refreshing the session's updated_at timestamp.

What is the best way to record mid-session scope changes and blockers?

Recording mid-session scope changes and blockers involves adding timestamped notes to state.json, ensuring traceability for decisions and new findings without altering the active lifecycle state.

Can I append timestamped notes to an active session without overwriting existing data?

Yes, appending timestamped notes to an active session is non-destructive, integrating into the existing state.json without overwriting previous entries while preserving all historical data.

How do I update the manifest with the latest session update time?

Updating the manifest with the latest session update time happens automatically when you log notes, refreshing the manifest's timestamp for quick session retrieval.

Does logging session updates alter the lifecycle state of state.json?

No, logging session updates does not alter the lifecycle state, as the process only appends to the updates array and modifies the updated_at timestamp within state.json.

Why should I use state.json for mid-session discoveries instead of standard logging?

Using state.json for mid-session discoveries preserves context within the session manifest, providing structured traceability for blockers and decisions that standard logging lacks.