meta-changelog

Record meta change-log entries for edits to Claude internal assets.

2|2|Updated Oct 1, 2017
One-click install
npx skills add https://github.com/pwr-piisw/wyklady --skill meta-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-changelog
Source: https://github.com/pwr-piisw/wyklady/tree/main/.claude/skills/meta-changelog
Command: npx skills add https://github.com/pwr-piisw/wyklady --skill meta-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record a meta change-log entry whenever Claude internal assets in this repo are added, modified, or removed. Triggers on edits to: .claude/skills/, .claude/agents/, .claude/commands/**, .claude/settings.json, .claude/settings.local.json, .mcp.json, CLAUDE.md (root or nested), or auto-memory files. Also triggers on direct user requests like "log this meta change", "add a meta entry", or "/meta-log". Writes one entry per logical change to meta/<YYYY-MM-DD-HHMM-slug>.md using templates/meta-entry.md, and updates meta/README.md so the new entry appears in the index.

Core Features & Use Cases

  • Change-log automation: automatically create a new meta entry for Claude internal asset changes.
  • Version tracking: keeps a chronological history of edits to assets that configure Claude behavior.
  • Use Case: When you update .claude/skills or CLAUDE.md, this skill records the change for accountability and traceability.

Quick Start

After finishing a logical change that affected Claude internal assets, run the skill to log the meta change.

Frequently Asked Questions about meta-changelog

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

FAQPage Schema
How do I automatically log changes to Claude internal assets like CLAUDE.md and settings files?

To automatically log changes to Claude internal assets, the skill monitors edits to paths like .claude/skills/** and CLAUDE.md, writing a meta change-log entry for each logical change. It generates timestamped markdown files and updates the index.

What is a meta change-log entry and when do I need one for version tracking?

A meta change-log entry records modifications to files that configure Claude behavior, such as .claude/settings.json or .mcp.json. You need one whenever these internal assets are added, modified, or removed to maintain accountability and traceability.

How to create a meta log entry after updating .claude/skills or .claude/agents directories?

After finishing a logical change to .claude/skills or .claude/agents, run the skill to log the meta change. It writes an entry to meta/<YYYY-MM-DD-HHMM-slug>.md using a template and updates meta/README.md so the new entry appears in the index.

Does this change-log automation tool support direct prompts like /meta-log?

Yes, this change-log automation supports direct user prompts. Triggering it with requests like "log this meta change", "add a meta entry", or "/meta-log" will generate a new chronological markdown entry and update the meta/README.md index.

Can I use this auditing skill to track edits to .mcp.json and nested CLAUDE.md files?

Yes, you can use this auditing skill to track edits to .mcp.json, root or nested CLAUDE.md files, .claude/settings.local.json, and auto-memory files. It applies to specified paths and records each modification for version tracking.

What are the limitations of using markdown files for Claude asset version tracking?

The limitation of using markdown files for Claude asset version tracking is that it creates one entry per logical change in meta/ directories. It functions as a chronological auditing index rather than providing automated rollback or conflict resolution capabilities.