process-sessions

Converts session notes into searchable digital text via OCR technology.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/tnez/docent --skill process-sessions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-sessions
Source: https://github.com/tnez/docent/tree/main/skills/docent/process-sessions
Command: npx skills add https://github.com/tnez/docent --skill process-sessions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git cli.

What problem does it solve?

AI agent session notes contain rich, detailed work logs that are ephemeral by nature. This Skill provides a structured process to review these sessions, extract high-value knowledge (decisions, discoveries, lessons learned), and integrate it into permanent project documentation, preventing knowledge loss and keeping your docs up-to-date.

Core Features & Use Cases

  • Session Review: Systematically scans and reviews AI agent session notes.
  • Knowledge Formalization: Extracts architecture decisions into ADRs, implementation insights into guides, and lessons learned into best practices.
  • Cleanup & Archiving: Manages session notes by archiving or deleting them after processing, maintaining a clean knowledge base.
  • Use Case: Your AI agent just completed a complex feature. Use this Skill to review the session notes, automatically generate an ADR for a key architectural choice, update the CHANGELOG with new features, and archive the detailed session log, ensuring all valuable context is preserved.

Quick Start

Process my recent AI agent session notes.

Frequently Asked Questions about process-sessions

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

FAQPage Schema
How do I extract knowledge from AI agent session notes into documentation?

Extract knowledge from session notes by reviewing .docent/sessions/*.md files, classifying insights into architecture decisions, implementation details, problems solved, and lessons learned, then transforming them into ADRs, guides, and documentation updates using structured formalization.

What's the best way to convert AI session logs into architecture decision records?

Review session notes for architectural choices, create ADRs via /docent:tell to formalize decisions, and publish insights to .docent/guides and relevant markdown files to integrate them into permanent project documentation.

Can I automate archiving session notes after extracting documentation?

Yes, this Skill enforces a cleanup workflow that archives or deletes processed session notes after knowledge extraction, maintaining a clean knowledge base while preserving extracted insights in permanent documentation.

How do I keep my project documentation synchronized with AI agent work?

Systematically scan AI session notes, extract valuable insights into ADRs and guides, update CHANGELOG.md and architecture docs with findings, then archive processed sessions to keep docs fresh and prevent knowledge loss.

Do I need git installed to process and archive session notes?

Yes, git cli is required as a dependency to manage session note archiving and documentation updates within the cleanup workflow.