log-change

Generate standardized markdown change logs for code modifications.

27|1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Till-Crazy-Tears-Us-Apart/Claude-Code-Engineering-Suite --skill log-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-change
Source: https://github.com/Till-Crazy-Tears-Us-Apart/Claude-Code-Engineering-Suite/tree/main/skills/log-change
Command: npx skills add https://github.com/Till-Crazy-Tears-Us-Apart/Claude-Code-Engineering-Suite --skill log-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill generates a standardized, detailed change log to ensure AI has a complete and accurate understanding of code modifications, crucial for context compression and version control.

Core Features & Use Cases

  • Structured Change Logging: Creates detailed logs following a strict template, including pre-implementation discussions, file-level modifications, and systemic impact analysis.
  • Data Integrity: Ensures all technical details, including failed hypotheses and risks, are documented for AI context.
  • Use Case: After implementing a new feature, use this Skill to generate a comprehensive log that captures every aspect of the change, ensuring the AI can accurately recall and reason about the modification in future interactions.

Quick Start

Use the log-change skill to generate a change log for task ID 'feature-123' with status 'completed'.

Frequently Asked Questions about log-change

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

FAQPage Schema
How do I generate a standardized changelog for AI context compression?

You create standardized changelogs for AI context by documenting pre-implementation discussions, file-level modifications, and systemic impact analysis within a strict markdown template. This structured documentation ensures AI accurately recalls and reasons about code modifications during future interactions.

What should be included in a code review changelog for version control?

A code review changelog for version control should include pre-implementation discussions, file-level impacts, failed hypotheses, and systemic effects. Documenting these technical details ensures complete data integrity and objective version tracking.

Why does an AI need a detailed change log for code modifications?

An AI needs a detailed change log to maintain a complete and accurate understanding of code modifications for context compression. Documenting failed hypotheses and systemic effects allows the AI to effectively recall and reason about past technical decisions.

How do I document systemic effects and failed hypotheses in software development?

You document systemic effects and failed hypotheses by applying a strict markdown template that captures pre-implementation discussions and file-level modifications. This objective documentation guarantees complete technical detail retention for AI context and version control.

Are there limitations to using strict markdown templates for change logging?

Using strict markdown templates for change logging requires meticulous documentation of all technical details, which may increase overhead in software development workflows. However, this strictness is necessary to ensure completeness and objectivity for AI context compression.