chat-history-convention

Append user messages to a local chat history log file.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/pelchers/SessionSaver --skill chat-history-convention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chat-history-convention
Source: https://github.com/pelchers/SessionSaver/tree/main/.codex/skills/chat-history-convention
Command: npx skills add https://github.com/pelchers/SessionSaver --skill chat-history-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Append every user message to .chat-history/user-messages.log with timestamp, role, and raw message body for project-local chat continuity.

Core Features & Use Cases

  • Ensures .chat-history/ exists at repo root.
  • Ensures .chat-history/user-messages.log exists.
  • Append each incoming user message with:
    • ISO timestamp
    • role=user
    • raw message content
  • Separate entries with ---

File Format

[2026-02-09T00:00:00Z] role=user
<raw message>

---

Quick Start

Use the chat history convention skill to append a message to the log.

Frequently Asked Questions about chat-history-convention

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

FAQPage Schema
How do I log user messages to a local file for chat continuity?

To log user messages for chat continuity, this Skill appends every incoming message to a local .chat-history/user-messages.log file at your repository root. It automatically creates the necessary directories and files to ensure persistent local transcripts across sessions.

What format is used when appending chat history to a local log file?

The chat history log format includes an ISO timestamp, the role=user tag, and the raw message content. Each appended entry in the user-messages.log file is separated by a horizontal rule (---) for easy visual parsing and quick review.

Does the chat history convention skill require PowerShell to append session logs?

The chat history convention supports a deterministic append workflow via a PowerShell script, but it primarily functions by ensuring the .chat-history/ directory exists and appending raw message bodies with timestamps directly to the log file.

How do I preserve project-wide session continuity across multiple repository chat sessions?

You preserve project-wide session continuity by appending every user message to a persistent local transcript. This Skill creates .chat-history/user-messages.log at the repo root to maintain a continuous record of raw message bodies and timestamps.

When do I need a local transcript file for repository chat sessions?

You need a local transcript file when your repository requires persistent local logs across sessions for quick review of user messages. It allows you to track project chat continuity by recording timestamped raw message content locally.