agent-change-documentation

Log agent-driven code changes in AGENT_CHANGES.md using a structured markdown template.

Updated Nov 21, 2025

Search Tags:#documentation #version control #agent workflow #code changes #audit trail #change log

Ready to run

npx skills add https://github.com/donchrillo/temu --skill agent-change-documentation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-change-documentation
Source: https://github.com/donchrillo/temu/tree/main/.opencode/skills/agent-change-documentation
Command: npx skills add https://github.com/donchrillo/temu --skill agent-change-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all code changes made by agents are meticulously documented, providing a clear audit trail and keeping documentation synchronized with the codebase.

Core Features & Use Cases

Structured Change Logging: Enforces a standardized format for documenting agent-driven code modifications.
Documentation Synchronization: Provides signals to a documentation agent to update relevant files.
Audit Trail: Creates a historical record of all agent changes for team reviews and compliance.
Use Case: After an agent implements a new feature, this skill guides the agent to log the change, specify affected files, and mark which documentation needs updating, ensuring transparency and maintainability.

Quick Start

Use the agent-change-documentation skill to log a recent code modification in the AGENT_CHANGES.md file.

Frequently Asked Questions about agent-change-documentation

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

FAQPage Schema

How do I maintain an audit trail for automated agent code changes?▼

To maintain an audit trail for agent code changes, you log modifications in a structured markdown file. This skill enforces logging within AGENT_CHANGES.md, capturing module details, change types, and impact for team review and compliance traceability.

What is the best way to document breaking changes introduced by an agent workflow?▼

Documenting breaking changes from an agent workflow requires a standardized markdown template. This skill enforces a structure in AGENT_CHANGES.md that explicitly flags breaking changes, descriptions, and affected modules for early detection during team reviews.

How do I keep documentation synchronized after agent-driven code modifications?▼

Keeping documentation synchronized after agent code modifications requires signaling a documentation agent to update relevant files. This skill provides those signals by recording affected documentation alongside the change log in AGENT_CHANGES.md.

Does this change logging approach require a specific markdown format?▼

Yes, this change logging approach requires adherence to a specific markdown template. The skill enforces a structured format in AGENT_CHANGES.md including fields for module, change type, description, affected documentation, impact, and breaking changes.

When do I need to use a structured change log for agent code changes?▼

You need a structured change log for agent code changes when you require traceability and compliance for team reviews. It is essential for maintaining an audit trail of agent-driven modifications and detecting breaking changes early in the development workflow.