update-report

Generate update reports documenting code and documentation changes.

Updated Jun 16, 2026

Search Tags:#project continuity #document update #code verification #update tracking #knowledge base management

Ready to run

npx skills add https://github.com/breakingcircuits1337/agent-skills --skill update-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-report
Source: https://github.com/breakingcircuits1337/agent-skills/tree/main/update-report
Command: npx skills add https://github.com/breakingcircuits1337/agent-skills --skill update-report

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages and verifies changes made to memory files and skills, ensuring updates are properly documented and tested before they impact system functionality.

Core Features & Use Cases

Documentation of Changes: Records file changes and the purpose behind them.
Verification Process: Offers a structured method for code and system verification before finalization.
Memory Updates: Provides guidelines for updating various memory files like CLAUDE.md, USER.md, and others, ensuring knowledge continuity.
Use Case: Before deploying a new version of a software tool, this skill guides you through updating the documentation, verifying the code, and updating the memory files accordingly.

Quick Start

Use the update-report skill to generate a new update report for the recent changes in your project.

Frequently Asked Questions about update-report

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

FAQPage Schema

How do I track documentation updates and verify code changes before deployment?▼

To track documentation updates and verify code changes, you generate a structured update report that records file modifications, their purpose, and guides you through a verification process before finalization.

What is the best way to maintain project continuity across multiple knowledge bases?▼

Maintaining project continuity across knowledge bases requires updating memory files like CLAUDE.md and USER.md with structured guidelines, ensuring that code and documentation changes are properly recorded and traceable.

How do I document the purpose of file changes in a software maintenance environment?▼

You document the purpose of file changes by creating an update report that records modifications and the reasoning behind them, automating the documentation process while requiring manual input for the change description.

Does code verification require manual input when updating memory files?▼

Yes, code verification requires manual input for the change description and verification steps, while the skill itself automates the surrounding documentation process for memory files like CLAUDE.md and USER.md.

Can I automate documentation updates for software development without manual verification?▼

You cannot fully automate documentation updates without manual verification, because this process requires manual input for change descriptions and code verification to ensure system functionality and traceability before deployment.