skills.rest
estevanhernandez-stack-ed
estevanhernandez-stack-edCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

session-logger

Implement two-phase append-only session logs with paired start and end entries.

Updated Apr 21, 2026
Search Tags:#plugin#instrumentation#jsonl#session-logging#start-end-tracing#session-uuid
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill session-logger-estevanhernandez-stack-ed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-logger
Source: https://github.com/estevanhernandez-stack-ed/vibe-test/tree/main/packages/vibe-test/skills/session-logger
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill session-logger-estevanhernandez-stack-ed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The session-logger provides a reliable, two-phase, append-only mechanism to track Vibe Test command runs by recording a sentinel entry at start and a terminal entry at end, linked by sessionUUID, enabling robust session memory and post-run analysis.

Core Features & Use Cases

  • Two-phase logging: emits a start and end entry for every command run.
  • Daily, local persistence: stores logs under ~/.claude/plugins/data/vibe-test/sessions as JSONL files, one per day.
  • Structured field contract: uses shared fields like sessionUUID, command, timestamp, and outcome, enabling easy correlation and evolution workflows.

Quick Start

Call start() when a command begins and end() when it finishes to record paired session entries.

Frequently Asked Questions about session-logger

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

FAQPage Schema
How do I implement two-phase session logging for command runs?▼

Two-phase session logging emits a start entry when a command begins and an end entry when it finishes, linked by sessionUUID. Logs are stored as daily JSONL files under ~/.claude/plugins/data/vibe-test/sessions for reliable post-run analysis.

What is the JSONL schema for append-only session logs?▼

The session log JSONL schema includes fields like schema_version, timestamp, sessionUUID, command, and outcome. Optional fields are populated at the end phase, enabling easy correlation and evolution workflows.

How do I track command start and end events using sessionUUID?▼

You track command events by calling start() when a command begins and end() when it finishes. These wrappers produce paired sentinel and terminal entries linked by sessionUUID for reliable session memory.

Does session-logger require external dependencies to store daily JSONL files?▼

Session-logger requires no external dependencies to store daily JSONL files. Logs are written locally under ~/.claude/plugins/data/vibe-test/sessions using the appendJsonl() file-writing workflow.

What is the best way to persist Vibe Test command runs locally for post-run analysis?▼

The best way to persist Vibe Test command runs is using an append-only daily JSONL file structure. This approach pairs start and end entries by sessionUUID, providing reliable local session memory for post-run analysis.

Related Skills

Explore More Software Engineering Skills→
Extremez-SuryaExtremez-Surya

vercel-plugin-eval

Execute Claude Code sessions to verify Vercel plugin hook behavior and coverage.

Community
Advanced
sentientspritesentientsprite

trading-analysis

Parse trading bot logs to extract performance metrics and generate Markdown reports.

Community
Intermediate
KanevryKanevry
50

quality-gates

Run typecheck, test, and lint quality gates across agent-driven sessions.

Community
Advanced
sarimofficialsarimofficial

session-state-manager

Save conversation state to an append-only log at .claude/state/session.md.

Community
Basic