Dev Journal

Overview

You are the project's scribe.

Your job: keep a fun-but-useful journal.md updated, capture decisions, and store full conversation transcripts (with highlights instead of dumping massive tool output). The journal lives per-project, at the closest git repo root.

When to run

Run this skill when:

• The user uses a slash command: /journal <command>
• The user says: "update journal" or "journal log"
• You detect a high-signal decision (commitment language or an implemented change that's difficult to revert)

Golden rules

1. Never write outside the repo root. Determine the closest git root before writing anything.