Clean Loop

Capture lessons learned, update documentation, and verify git state after tasks.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Totes-MickGOATs/r8eo-x-unity --skill clean-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Clean Loop
Source: https://github.com/Totes-MickGOATs/r8eo-x-unity/tree/main/.agents/skills/clean-loop
Command: npx skills add https://github.com/Totes-MickGOATs/r8eo-x-unity --skill clean-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that at the end of every task, all lessons learned are captured, documentation is updated, and the git state is clean, preventing knowledge loss and maintaining project integrity.

Core Features & Use Cases

  • Lessons Learned Capture: Systematically reviews task outcomes to identify and record what went wrong, what was surprising, and what worked well.
  • Documentation Sweep: Verifies and updates CLAUDE.md files in modified directories to reflect current project state.
  • Memory Management: Captures user feedback, project context, and external references into organized memory files.
  • Git State Audit: Ensures no uncommitted changes remain and checks for sensitive files.
  • Status Update: Updates project manifests and status files if the task altered the system's state.
  • Use Case: After completing a complex bug fix, you run Clean Loop to document the unexpected behavior encountered, update the relevant CLAUDE.md with the fix details, save a new memory about a useful debugging technique, and ensure your branch is clean before merging.

Quick Start

Run the clean loop skill to capture lessons learned, update documentation, and verify git state.

Frequently Asked Questions about Clean Loop

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

FAQPage Schema
How do I automate knowledge capture and documentation updates at the end of a task?

End-of-task knowledge capture is automated by systematically reviewing task outcomes, updating CLAUDE.md files in modified directories, and recording lessons learned to preserve project context. This prevents knowledge loss and maintains repository integrity.

How do I verify my git state is clean after completing a complex bug fix?

Git state verification is performed by auditing the repository for uncommitted changes and checking for sensitive files before merging. This ensures the project repository remains clean, auditable, and free of unintended modifications.

What is the best way to capture lessons learned during software development?

Lessons learned are captured by systematically reviewing task outcomes to identify what went wrong, what was surprising, and what worked well. This feedback and project context are then saved into organized memory files.

Does this documentation cleanup process update project status files automatically?

Documentation sweeps and status updates are applied if the task altered the system's state. Project manifests and status files are updated alongside CLAUDE.md files to reflect the current project state accurately.

How do I manage project memory and external references after finishing a coding task?

Project memory management involves capturing user feedback, project context, and external references into organized memory files. This ensures important contextual details and debugging techniques are preserved for future tasks.