reflect

Capture session learnings and update PROGRESS.md from git history.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/severeon/neuroscript-rs --skill reflect-severeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/severeon/neuroscript-rs/tree/main/.claude/skills/ns-reflect
Command: npx skills add https://github.com/severeon/neuroscript-rs --skill reflect-severeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps work continuity by turning ephemeral session activity into a concise, discoverable project history so future sessions can pick up where they left off without losing context.

Core Features & Use Cases

  • Automated session synthesis: Reads recent git history and any pending reflection markers to produce a structured session entry.
  • Project progress bookkeeping: Appends a full session entry to docs/PROGRESS.md and a condensed note to .claude/context/session-reflections.md for long-term knowledge accumulation.
  • Light-weight cleanup: Removes the pending reflection marker after successful capture to avoid duplicate work.
  • Use Case: After a focused development session on NeuroScript, generate a top-of-file PROGRESS.md entry summarizing commits, changed files, lessons learned, limitations, and next steps.

Quick Start

Summarize the last session by reading recent commits and any pending reflection note, then append a formatted entry to docs/PROGRESS.md and a condensed item to .claude/context/session-reflections.md.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I document git commits and session notes into PROGRESS.md?

To document git commits into PROGRESS.md, this skill reads recent git history and pending reflection markers to append a structured session entry summarizing changed files and lessons learned.

What is the best way to maintain project continuity between development sessions?

The best way to maintain project continuity is to capture session learnings by appending condensed notes to .claude/context/session-reflections.md, ensuring future sessions can resume work without losing context.

How does automated session synthesis work for repository documentation?

Automated session synthesis works by reading recent git commits and pending reflection notes to produce a structured top-of-file PROGRESS.md entry, then removing the marker to avoid duplicate work.

Do I need git history access to generate session reflections?

Yes, you need git history access to generate session reflections, as the skill requires recent commit data and .claude/context files to summarize file changes and append them to project documentation.

Can I use this to summarize changed files and limitations after a coding session?

Yes, you can use this to summarize changed files and limitations after a coding session by generating a top-of-file PROGRESS.md entry that details commits, lessons learned, and next steps.

What limitations exist when capturing session notes for project history?

A limitation is that session note capture applies specifically to developer sessions in the NeuroScript repository, relying on docs/PROGRESS.md and pending reflection markers for knowledge accumulation.