skills.rest
Immanuel-Aristotle
Immanuel-AristotleCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

session-log

Append prompts, responses, commands, and file changes to AGENT.log.md.

Updated Apr 27, 2026
Search Tags:#codex#commands#session#reproducibility#log#agent-log
One-click install
npx skills add https://github.com/Immanuel-Aristotle/agents --skill session-log-immanuel-aristotle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-log
Source: https://github.com/Immanuel-Aristotle/agents/tree/main/skills/session-log
Command: npx skills add https://github.com/Immanuel-Aristotle/agents --skill session-log-immanuel-aristotle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a canonical, chronological record of the Codex session in AGENT.log.md, capturing prompts, responses, commands, and file changes to aid debugging and review.

Core Features & Use Cases

  • Append session entries to AGENT.log.md, preserving history across commands and interactions.
  • Reconstruct the current Codex session context from prompts, assistant replies, and shell activity when needed.
  • Optional extension: track added/modified/deleted files per command if determinable.

Quick Start

Ask the assistant to start recording your Codex session to .agents/AGENT.log.md.

Frequently Asked Questions about session-log

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

FAQPage Schema
How do I maintain a Codex session log for debugging and review?▼

To maintain a Codex session log, you can append chronological entries to an AGENT.log.md file, capturing prompts, responses, commands, and file changes to aid debugging and review.

What is the best way to reconstruct Codex session context from shell activity?▼

The best way to reconstruct Codex session context is by preserving a chronological trace of prompts, assistant replies, and shell activity in a canonical log file without overwriting prior entries.

How do I track file changes per command during an interactive coding session?▼

You can track file changes per command during an interactive coding session by appending added, modified, and deleted file records to an ongoing session log if determinable.

Does appending session logs to AGENT.log.md overwrite previous history?▼

Appending session logs to AGENT.log.md does not overwrite previous history; it ensures non-destructive logging by preserving past entries while reconstructing current context.

Can I use a session log for collaborative exploration and debugging sessions?▼

Yes, you can use a session log for ongoing coding, debugging sessions, and collaborative exploration where a trace of prompts, responses, commands, and file changes is required.

How to start recording a Codex session to preserve history across commands?▼

To start recording a Codex session and preserve history across commands, ask the assistant to begin appending session entries to the .agents/AGENT.log.md file.

Related Skills

Explore More Software Engineering Skills→
GiantCroissant-LunarGiantCroissant-Lunar

dev-log

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

Official
Advanced
bordenetbordenet
8

timeline-trace-investigator

Reconstruct incident timelines from distributed traces, logs, deployments, and metrics.

Community
Advanced
martiendejongmartiendejong
1

session-reflection

Log coding session learnings into a persistent reflection.log.md file.

Community
Basic
AbilityaiAbilityai
103

update-changelog

Appends session modifications to a master changelog markdown file for version control.

Official
Basic