skills.rest
GiantCroissant-Lunar
GiantCroissant-LunarOFFICIAL
Explore all skills by this author →
GitHub

dev-log

Record structured dev-log entries with YAML frontmatter under vault/dev-log.

Updated Apr 16, 2026
Search Tags:#automation#documentation#logging#governance#session#dev-log
One-click install
npx skills add https://github.com/GiantCroissant-Lunar/proto-breakout --skill dev-log-giantcroissant-lunar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-log
Source: https://github.com/GiantCroissant-Lunar/proto-breakout/tree/main/.agent/skills/00-meta/dev-log
Command: npx skills add https://github.com/GiantCroissant-Lunar/proto-breakout --skill dev-log-giantcroissant-lunar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records a structured dev-log at the end of every working session to create a persistent, human-readable trail of work across all agents and sessions.

Core Features & Use Cases

  • End-of-session logging for commits, edits, and research
  • One file per session stored under vault/dev-log/YYYY-MM-DD-{slug}.md
  • YAML frontmatter for metadata and a consistent log format for easy querying
  • Integrates with autoloop and validation guards to ensure timely logging

Quick Start

End each session by creating a new vault/dev-log entry describing what was accomplished.

Frequently Asked Questions about dev-log

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

FAQPage Schema
How do I automate session logging for development work?▼

Session logs are stored as one file per session under vault/dev-log/YYYY-MM-DD-{slug}.md, using a YAML frontmatter for metadata and a consistent log format for easy querying and governance.

What metadata should a structured dev-log include for governance?▼

A structured dev-log for governance should include a YAML frontmatter with metadata and a fixed log format capturing the date, agent, branch, version, and decisions made during the session.

Can I enforce end-of-session logging across multiple agents?▼

Yes, you can enforce end-of-session logging across multiple agents by integrating with autoloop and validation guards to ensure timely logging after commits, edits, and research sessions.

Does session logging work without external dependencies?▼

Session logging works without external dependencies, relying solely on a per-session file pattern under vault/dev-log/YYYY-MM-DD-{slug}.md with YAML frontmatter to maintain a persistent trail of work.

What is the best way to create a human-readable trail of work across sessions?▼

The best way to create a human-readable trail of work is recording a structured dev-log at the end of every working session, using a consistent log format with date, agent, branch, version, and decisions.

Related Skills

Explore More Content & Communication Skills→
OmarHosamCodesOmarHosamCodes
1

wiki-setup

Initialize and configure an Obsidian wiki vault with standardized folders and templates.

Community
Intermediate
maxvaegamaxvaega
146

nested-deep-skill

Locate SKILL.md files in nested directories and extract metadata for indexing.

Community
Basic
technomenschtechnomensch
5

session-wrap

Detect session stopping points and prompt summaries of work progress.

Community
Basic
eysenfalkeysenfalk

checkpoint

Captures git status, modified files, and task states into a JSON checkpoint file.

Community
Intermediate