skills.rest
nakane1chome
nakane1chomeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-record

Capture per-session agent activity into JSON audit artifacts via hooks.

1|Updated Feb 8, 2026
Search Tags:#audit#hooks#jsonl#session-logging#dev-record#agent-self-reporting
One-click install
npx skills add https://github.com/nakane1chome/claude-skills --skill dev-record
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-record
Source: https://github.com/nakane1chome/claude-skills/tree/main/skills/dev-record
Command: npx skills add https://github.com/nakane1chome/claude-skills --skill dev-record

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing, auditing, and improving Claude Code workflows requires a transparent record of what happened during sessions. Dev Record provides passive, verifiable logging of prompts, tool usage, decisions, and deviations to support post-hoc analysis and governance.

Core Features & Use Cases

  • Passive session logging via hooks that record user input, tool calls, tool results, and plan snapshots.
  • Generates per-session summaries and extractable event logs into audit/dev_record and audit/ops_record for traceability.
  • Simple project setup with install.sh to initialize gitignore, CLAUDE.md guidance, and audit directories.

Quick Start

Run the install.sh script from this skill's directory to initialize the project for dev-record.

Frequently Asked Questions about dev-record

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

FAQPage Schema
How do I create an audit trail of Claude Code sessions for post-hoc analysis?▼

Session logging records per-session agent activity during Claude Code sessions, capturing plans, prompts, decisions, and deviations. It uses hooks to passively record user input, tool calls, and plan snapshots for transparent, verifiable traceability.

What's the best way to log agent decisions and deviations during code generation?▼

Logging agent decisions is achieved by applying hooks at the project level that passively capture user input, tool usage, and deviations. A finalization step then produces JSON artifacts for traceability and post-hoc analysis.

How do I set up session-logging hooks for my project?▼

Project setup for session-logging hooks requires running the install.sh script, which initializes gitignore, CLAUDE.md guidance, and audit directories. This configures the environment to capture agent activity and output JSON artifacts.

Where are Claude Code session logs and audit artifacts stored?▼

Session logs and audit artifacts are stored under the audit/dev_record and audit/ops_record directories within your project. These locations hold the generated per-session summaries and extractable event logs for review.

Does session logging for Claude Code require any external dependencies?▼

No external dependencies are required. The session logging relies on the dev-record plugin, related hooks, and project setup via install.sh to passively capture agent activity and generate JSON artifacts without additional packages.

Related Skills

Explore More Software Engineering Skills→
az9713az9713

dark-code-suite-init

Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.

Community
Intermediate
xcriminal1xcriminal1

session-logs

Locate and analyze your own session logs in JSONL files.

Community
Intermediate
pabloimrik17pabloimrik17

hookify

Convert CLAUDE.md instructions into enforceable Claude Code hooks.

Community
Advanced
ThiNepoThiNepo
2

langchain-middleware

Implement human-in-the-loop approval workflows for LangChain agents.

Community
Advanced