coding-worklog-obsidian

Document coding sessions as structured Obsidian notes with YAML frontmatter.

7|2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ChaosEmily/book-pipeline --skill coding-worklog-obsidian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-worklog-obsidian
Source: https://github.com/ChaosEmily/book-pipeline/tree/main/.agent/skills/coding-worklog
Command: npx skills add https://github.com/ChaosEmily/book-pipeline --skill coding-worklog-obsidian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coding projects often generate scattered notes and weak linkage between decisions, issues, and sessions in Obsidian, making it hard to review progress or trace root causes. This skill creates structured, YAML-frontmatter notes for each coding session and establishes bidirectional links, so your knowledge graph stays coherent over time.

Core Features & Use Cases

  • Structured session notes with YAML frontmatter for easy querying and consistent record-keeping.
  • Bidirectional linking between sessions, decisions, and issues using Obsidian links to build a traceable knowledge graph.
  • Dataview-ready metadata that enables quick analytics and reports (velocity, issue statuses, decisions).
  • Progressive disclosure workflow: load module guidance on demand to keep context window lean and focused.

Quick Start

Complete a coding session and trigger the skill to generate an Obsidian note with YAML frontmatter, then link to related decisions and issues.

Frequently Asked Questions about coding-worklog-obsidian

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

FAQPage Schema
How do I create structured Obsidian work logs for coding sessions?

Obsidian work logs use YAML frontmatter and bidirectional links to document coding sessions. This structure connects sessions, decisions, and issues, making your development knowledge graph traceable and queryable over time.

How do I make coding session notes queryable with Dataview in Obsidian?

Coding session notes become Dataview-queryable by embedding structured YAML frontmatter in each Obsidian note. This metadata enables quick analytics and reports for tracking velocity, issue statuses, and decision history.

Can I link coding session notes to decisions and issues in an Obsidian vault?

You can link coding session notes to decisions and issues using Obsidian bidirectional links. This builds a traceable knowledge graph connecting your session records directly to related project decisions.

What is the best way to organize an Obsidian vault for progressive disclosure of coding worklogs?

Organize coding worklogs using a vault layout that supports progressive disclosure by loading module guidance on demand. This keeps the context window lean while maintaining structured YAML frontmatter and bidirectional links.

Do I need Dataview to track coding project velocity in Obsidian?

Dataview is required to query the YAML frontmatter metadata in your coding worklogs for quick analytics. It enables generating reports on project velocity, issue statuses, and decisions from your Obsidian vault.

Why do my scattered Obsidian coding notes lose traceability over time?

Scattered Obsidian coding notes lose traceability due to weak linkage and missing YAML frontmatter between sessions, decisions, and issues. Structured worklogs solve this by building a coherent, queryable knowledge graph.