evolution-changelog

Record evolution-driven changes with date-stamped entries in EVOLUTION.md.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danmestas/wardrobe --skill evolution-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution-changelog
Source: https://github.com/danmestas/wardrobe/tree/main/skills/evolution-changelog
Command: npx skills add https://github.com/danmestas/wardrobe --skill evolution-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill maintains EVOLUTION.md at the repo root to record which evolution-driven changes were applied, when they occurred, and why, closing the loop between proposals and repository history.

Core Features & Use Cases

  • Automatic logging of evolution-driven changes with date-stamped entries.
  • Consistent, grep-friendly markdown format that supports auditing.
  • Integrates with evolution proposals and tool hooks to ensure changes are captured.

Quick Start

Log an evolution-driven change by updating EVOLUTION.md whenever an evolution patch is applied.

Frequently Asked Questions about evolution-changelog

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

FAQPage Schema
How do I maintain a changelog for automated git history changes?

To maintain a changelog for automated git history changes, this skill updates an EVOLUTION.md file at the repository root with timestamped entries, recording patches and rationale for evolution-driven edits.

What is the markdown format for an EVOLUTION.md changelog file?

The EVOLUTION.md changelog file uses a strict markdown flat-line format with date sections and per-entry fields, ensuring consistent history tracking and grep-ability for auditing evolution-driven changes.

Why use a dedicated evolution changelog instead of standard git commit logging?

A dedicated evolution changelog closes the loop between proposals and repository history by recording when and why evolution-driven changes were applied, providing a human-readable and grep-friendly audit trail that standard git commit logging lacks.

How do I log evolution-driven patches with dates and rationale?

You log evolution-driven patches with dates and rationale by updating the EVOLUTION.md file whenever an evolution patch is applied, automatically capturing the date, patch details, and reasoning in consistent markdown sections.

Does the evolution changelog support grep-friendly markdown auditing?

Yes, the evolution changelog supports grep-friendly markdown auditing by implementing a strict flat-line format with structured date sections and per-entry fields, ensuring consistent history tracking across daily development.