Extract knowledge from journal entries into ADRs and guides.
npx skills add https://github.com/tnez/docent --skill process-journals
Please help me install this Agent Skill. Skill: process-journals Source: https://github.com/tnez/docent/tree/main/skills/docent/process-journals Command: npx skills add https://github.com/tnez/docent --skill process-journals
Raw journal entries and notes often contain valuable insights that get lost over time if not formalized. This Skill provides a systematic workflow to review these ephemeral records, extract critical architecture decisions, implementation insights, and project context, and integrate them into permanent, searchable documentation.
Process my recent journal entries and extract key knowledge.
High-intent search queries and answers about installing and using this skill.
Extract architecture decisions by reviewing journal entries for key decisions, then generate ADRs that capture the decision, rationale, date, and alternatives considered. This Skill automates the process of identifying and formalizing these decisions into permanent, searchable documentation.
Process your notes systematically to identify valuable insights, then transform them into structured outputs like ADRs, guides, READMEs, and troubleshooting docs. The Skill extracts implementation insights and project context, organizing them into formal documentation while archiving processed entries.
Yes. This Skill automates reviewing journal entries, extracting critical discoveries, generating ADRs for decisions, updating guides with insights, and committing changes to git. It produces a summary report and archives processed journals, keeping your knowledge base clean and current.
After processing journals to extract knowledge, the Skill archives or deletes processed entries based on your configuration. This cleanup keeps your active knowledge base organized while preserving extracted insights in formal documentation.
Journals should document architecture decisions with context, implementation discoveries, rationale, patterns identified, and problems solved. The Skill identifies this valuable content and formalizes it into ADRs, guides, and troubleshooting docs for permanent reference.
Yes. Git CLI is required to commit the changes produced by processing journals—including new ADRs, updated documentation, changelog entries, and archived journal records.
tnezInitialize the .docent directory structure and configuration for new projects.
JeremyDev87Generate READMEs, API docs, ADRs, and CHANGELOGs from repository structure.
dudusoarGenerate Conventional Commits messages and update GIT_LOG.md documentation.
channingwaltonRead and write Obsidian vault notes with WikiLinks and templates.
