history-hygiene

Record only final confirmed outcomes in markdown history files.

Updated Apr 3, 2026

Search Tags:#documentation #markdown #history #team collaboration #decision log #source of truth #stale entries

Ready to run

npx skills add https://github.com/sachinnair90/gitgloss --skill history-hygiene-sachinnair90

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents history files from becoming misleading by ensuring they record only the final confirmed outcome, not early requests, temporary ideas, or later reversals.

Core Features & Use Cases

Final-state logging: Capture what actually happened so future readers do not inherit stale or incorrect decisions.
Revision awareness: Update entries immediately when a plan changes, instead of leaving outdated language behind.
Single-source clarity: Write history entries that stand on their own and do not require cross-referencing other files.
Use Case: A team initially discusses one release target, then changes direction later; this Skill helps you document the final decision accurately so the record stays trustworthy.

Quick Start

Use the history-hygiene skill to rewrite the history entry so it reflects the final confirmed outcome and removes any intermediate or reversed decision.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema

How do I keep markdown history files accurate when team decisions change direction?▼

Decision logs become misleading when stale entries are left behind after a plan changes, causing future readers to inherit outdated or incorrect decisions instead of the actual final outcome.

How do I write a decision log entry that stands on its own without cross-references?▼

Rewrite the history entry so it reflects the final confirmed outcome and removes any intermediate or reversed decisions, ensuring the markdown file captures only what actually happened.

Can I use this approach for team collaboration workflows that track spawns and outcomes?▼

Yes, it applies directly to team collaboration workflows tracking decisions, spawns, and outcomes by enforcing confirmation before logging and ensuring history files reflect only the final confirmed outcome.

Why does my history file show outdated language after a release target reversal?▼

Outdated language appears because intermediate decisions were logged without immediate updates; this approach fixes it by rewriting entries to reflect only the final confirmed outcome and removing reversed directions.