Document AI-assisted coding sessions into summaries, ADRs, and change logs.
npx skills add https://github.com/gil-air-may/scribe --skill session-scribe
Please help me install this Agent Skill. Skill: Session Scribe Source: https://github.com/gil-air-may/scribe/tree/main Command: npx skills add https://github.com/gil-air-may/scribe --skill session-scribe
This Skill transforms ephemeral AI coding sessions into structured, persistent documentation, capturing architectural decisions, reasoning, and context evolution, preventing valuable insights from being lost.
@scribe to automatically generate a session summary, document any architectural decisions made, and save it for future reference or team review.Use the scribe skill to document your current coding session.
High-intent search queries and answers about installing and using this skill.
To document AI coding sessions automatically, this Skill observes file modifications and extracts conversational context into structured artifacts like session summaries and change logs. It captures architectural decisions and reasoning during development to preserve valuable insights.
Generating Architectural Decision Records (ADRs) is handled by extracting conversational context from coding sessions to document key architectural choices and their rationale. It transforms ephemeral AI coding interactions into persistent, structured documentation.
To save code context and session logs, the Skill indexes project keywords and saves generated documentation within a dedicated repository. This facilitates context retrieval for ongoing development and allows recalling previous session decisions.
Automatic session logging tracks file modifications by observing changes during AI-assisted coding sessions. It uses these modifications to extract conversational context and automatically generate session summaries and change logs for your projects.
A dedicated documentation repository is supported to store session summaries and Architectural Decision Records. This structure ensures that generated change logs and context artifacts are organized for future reference and team review.
Automatic session documentation relies on observing file modifications and extracting conversational context to build artifacts. It requires active coding sessions to capture decisions and reasoning, meaning it cannot document historical development that occurred prior to initialization.
koasis89Manage persistent markdown knowledge bases with keyword search and lifecycle tracking.
fukukei23Record project decisions and session outcomes into structured markdown documentation.
BugRogerParse Today.md files to extract frontmatter, sections, and entities.
GainInsightDevCreate and manage Architecture Decision Records with templates and an index.