enable-journaling

Install opt-in PostToolUse hook scripts for metadata-only journaling of Claude Code tool calls.

4|3|Updated May 2, 2026
One-click install
npx skills add https://github.com/ggemba/squad-mcp --skill enable-journaling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enable-journaling
Source: https://github.com/ggemba/squad-mcp/tree/main/skills/enable-journaling
Command: npx skills add https://github.com/ggemba/squad-mcp --skill enable-journaling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you opt in to automatic journaling of tool-call activity as local metadata, so you can build a reliable work-trail without manually tracking what happened.

Core Features & Use Cases

  • Metadata-only capture: records timestamp, tool name, and edited file path, and explicitly avoids storing file contents.
  • Opt-in PostToolUse plumbing: installs bundled PostToolUse hook scripts into .squad/hooks/ after explicit consent.
  • No automatic Claude Code edits: prints the .claude/settings.json PostToolUse snippet for the user to paste, without writing it.

Quick Start

Ask the user to run /squad:enable-journaling and confirm that the hook scripts should be copied into .squad/hooks/ so they can paste the settings snippet into .claude/settings.json.

Frequently Asked Questions about enable-journaling

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

FAQPage Schema
How do I set up a local audit trail for Claude Code tool calls?

To set up a local audit trail, you opt into metadata-only journaling by installing PostToolUse hook scripts that record timestamps, tool names, and file paths into a local JSONL work-trail during interactive editor sessions.

Does Claude Code journaling capture store file contents or just metadata?

Claude Code journaling capture is metadata-only, explicitly recording the timestamp, tool name, and edited file path without storing any actual file contents to maintain privacy and reduce storage overhead.

How do I enable PostToolUse hooks for workflow automation without modifying settings automatically?

You enable PostToolUse hooks by running the enable-journaling command, granting consent to copy scripts into `.squad/hooks/`, and manually pasting the provided settings snippet into `.claude/settings.json` since the Skill never auto-writes it.

Can I track Edit and Write events automatically in my interactive editor sessions?

Yes, you can track Edit and Write events automatically by installing the opt-in PostToolUse hook scripts that generate a local JSONL work-trail without changing your existing squad behavior.

Why does the enable-journaling process require explicit consent before writing hook scripts?

The enable-journaling process requires explicit consent to ensure you maintain control over file writes, confining state mutation strictly to `.squad/hooks/` and preventing unauthorized modifications to your `.claude/settings.json` configuration.

What do I need to configure in `.claude/settings.json` to start capturing tool-call metadata?

You need to paste the PostToolUse configuration snippet provided by the Skill into `.claude/settings.json` after confirming the installation of hook scripts into `.squad/hooks/` to begin capturing tool-call metadata.