history-hygiene

Name: history-hygiene
Availability: InStock
Author: jperezdelreal

Record final outcomes to history.md and update reversed decisions.

Updated Apr 6, 2026

Search Tags:#documentation #collaboration #history #truth #postmortem #decision-logging

Ready to run

npx skills add https://github.com/jperezdelreal/GymBro --skill history-hygiene-jperezdelreal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill history-hygiene-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History files often capture intermediate decisions or draft notes. This skill ensures that history.md records only the final outcomes to maintain a single source of truth.

Core Features & Use Cases

Records the final outcome to history.md and updates it when decisions are reversed.
Supports team collaboration by preserving a consistent, auditable decision trail.
Useful for postmortems and retrospectives where accuracy of final conclusions matters.

Quick Start

Record a final outcome to history.md after the decision is confirmed.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema

How do I record only final outcomes in decision logging for postmortems?▼

Decision logging for postmortems records final outcomes to history.md, updating immediately if decisions are reversed, ensuring a single source of truth without intermediate draft entries.

What is the best way to maintain a single source of truth for collaborative project history?▼

A single source of truth for collaborative project history is maintained by logging only confirmed final outcomes to history.md, omitting intermediate requests or reversed decisions to preserve an auditable decision trail.

How do I update history.md when a collaborative AI decision is reversed?▼

When a collaborative AI decision is reversed, history.md is updated immediately to reflect the new final outcome, preventing outdated draft notes from polluting the auditable decision trail.

Why does my decision log contain intermediate requests instead of final conclusions?▼

Decision logs contain intermediate requests when draft notes are recorded prematurely. Enforcing final-outcome logging ensures history.md captures only confirmed conclusions, preventing reversed decisions from cluttering project retrospectives.

When do I need to enforce final-outcome logging for incident post-mortems?▼

Final-outcome logging is needed for incident post-mortems when accuracy of actual conclusions matters, ensuring history.md reflects confirmed decisions rather than intermediate requests or draft notes.

Can I use history.md for team collaboration without creating draft entries?▼

Yes, history.md supports team collaboration by enforcing final-outcome logging without draft entries, preserving a consistent and auditable decision trail that reflects only actual conclusions.