journal

Record completed implementation phases in a .journal/ directory with file changes.

Updated Mar 12, 2026

Search Tags:#documentation #version control #logging #journal #compiler #implementation log

Ready to run

npx skills add https://github.com/SarthakMishra/oxc-react-compiler --skill journal-sarthakmishra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: journal
Source: https://github.com/SarthakMishra/oxc-react-compiler/tree/main/.claude/skills/journal
Command: npx skills add https://github.com/SarthakMishra/oxc-react-compiler --skill journal-sarthakmishra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way to maintain a chronological log of implementation work, ensuring that key decisions, technical details, and file changes are meticulously recorded for future reference and auditing.

Core Features & Use Cases

Phase Entry Recording: Document each distinct phase of work with details on tasks, upstream references, and technical narratives.
File Change Tracking: Maintain tables of newly created and modified files for each phase.
Use Case: After completing a significant refactoring of a compiler pass, use this Skill to create a new journal entry detailing the changes, the rationale behind them, and listing all affected files.

Quick Start

Use the journal skill to record the completion of a compiler pass.

Frequently Asked Questions about journal

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

FAQPage Schema

How do I maintain a chronological implementation log for compiler passes?▼

To maintain a chronological implementation log for compiler passes, record completed work as phase entries in a .journal/ directory, documenting technical narratives, file changes, and upstream references.

What is the best way to document file changes and technical decisions during a refactor?▼

The best way to document file changes and technical decisions during a refactor is to create journal entries detailing the rationale, newly created files, modified files, and upstream references in a structured directory.

Can I use a structured journal to track implementation progress for new features?▼

Yes, you can use a structured journal to track implementation progress for new features by maintaining tables of file changes and recording technical narratives for each distinct phase of work.

Does recording implementation progress require sequential phase numbering and specific date formatting?▼

Yes, recording implementation progress requires sequential phase numbering and specific date formatting to ensure chronological consistency and accurate auditing of file changes and technical narratives.

How do I link journal entries to existing .todo items when logging implementation work?▼

To link journal entries to existing .todo items when logging implementation work, include direct links to the .todo items within the phase entries to maintain traceability between planning and execution.

What limitations should I expect when logging file changes in a .journal/ directory?▼

When logging file changes in a .journal/ directory, you must adhere to strict sequential phase numbering and specific date formatting, meaning manual formatting errors can disrupt the chronological audit trail.