dev-log

Create and update daily Dev Log entries in an Obsidian vault.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill dev-log-rafayelgardishyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-log
Source: https://github.com/RafayelGardishyan/rafayels-marketplace/tree/main/plugins/rafayels-engineering/.opencode/skills/dev-log
Command: npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill dev-log-rafayelgardishyan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers keep a consistent, up-to-date Dev Log by automatically creating or updating daily entries in an Obsidian vault after significant work or PR merges.

Core Features & Use Cases

  • Automatic daily entries: Creates or updates the log for the current date with a reference to recent work.
  • PR/feature context: Incorporates PR titles or feature names to provide context in the log.
  • Template-driven: Enforces a standardized structure for what changed and decisions.

Quick Start

Create or update today's dev log entry in the Obsidian vault using the current date as the filename.

Frequently Asked Questions about dev-log

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

FAQPage Schema
How do I automate daily Dev Log entries in Obsidian after a PR merge?

You can automate daily Dev Log entries in Obsidian by using a template-driven workflow that creates or updates the current date's file with PR titles and feature context immediately after a merge.

Does the Dev Log automation work with Obsidian frontmatter and date-based filenames?

Yes, the Dev Log automation operates directly on Obsidian frontmatter templates and uses the current date as the filename to enforce a standardized structure for daily entries.

Can I include PR numbers and feature names in my Obsidian daily log template?

Yes, you can include an optional PR number or feature name to provide context, which the workflow automatically incorporates into the standardized structure of your daily log template.

What is the best way to keep a development workflow log updated with merged PRs?

The best way to keep a development workflow log updated with merged PRs is to automate the process, triggering daily log creation or updates that reference recent work and decisions after major feature completions.

Do I need any dependencies to automate Obsidian vault updates for my dev log?

No dependencies are required to automate Obsidian vault updates for your dev log, as the workflow directly handles file creation and frontmatter updates without external extensions.