devlog

Summarize coding sessions and append progress notes to Obsidian daily notes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BaeHenryS/personal-toolkit --skill devlog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devlog
Source: https://github.com/BaeHenryS/personal-toolkit/tree/main/plugins/vault/skills/devlog
Command: npx skills add https://github.com/BaeHenryS/personal-toolkit --skill devlog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly summarize a coding session, log progress, and maintain a consistent daily-note workflow by exporting transcripts and generating a vault-friendly summary.

Core Features & Use Cases

  • Session summarization: Produce a concise progress note based on chat history and actions performed during a coding session.
  • Obsidian integration: Append a focused progress entry to today's Obsidian daily note under the project's section, with a link to the full external session log.
  • External export & vault summary: Persist transcripts to a structured external storage folder and generate a lightweight vault summary for quick reference.

Quick Start

Use the /devlog command to summarize your latest coding session and push a single concise accomplishment to the daily note.

Frequently Asked Questions about devlog

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

FAQPage Schema
How do I automatically summarize coding sessions and export transcripts to Obsidian daily notes?

To summarize coding sessions and export transcripts to Obsidian, you can trigger a command that generates a concise progress note, appends it to today's daily note, and saves full session logs to external storage.

What's the best way to log development progress directly into an Obsidian vault?

Logging development progress into an Obsidian vault is done by appending a concise accomplishment summary to today's daily note under the relevant project section, alongside a link to the full session transcript.

Do I need a vault-config.yaml file to append session logs to Obsidian daily notes?

Yes, you need a vault-config.yaml file to locate the Obsidian vault and read daily notes and project structures, ensuring the session summary is appended to the correct project section.

How does external transcript export work for Obsidian session logs?

External transcript export works by persisting full session histories to a structured external storage folder, generating a lightweight vault summary with a link back to the original session log for reproducible context.

Can I generate a reproducible context link between Obsidian daily notes and full session transcripts?

Yes, generating a reproducible context link is supported by appending a concise progress entry to the daily note that references the full external session log stored in the configured external storage folder.

Why are my coding session summaries not appending to the correct project section in Obsidian?

Coding session summaries fail to append correctly when the vault-config.yaml lacks accurate project structure definitions or the Obsidian vault path settings are misconfigured, preventing proper daily note targeting.