skills.rest
WayneWalterBerry
WayneWalterBerryCOMMUNITY
Explore all skills by this author →
GitHub

history-hygiene

Record final, confirmed decisions to history.md after they are made.

Updated Mar 19, 2026
Search Tags:#versioning#documentation#logging#history#team-collaboration#decision-trail
One-click install
npx skills add https://github.com/WayneWalterBerry/MMO --skill history-hygiene-waynewalterberry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-hygiene
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.copilot/skills/history-hygiene
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill history-hygiene-waynewalterberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History logs often become polluted with intermediate requests or reversed decisions, causing future agents to infer the wrong outcome. History hygiene ensures that only the final, confirmed decisions are written to history.md, preserving a reliable record for audits and downstream tasks.

Core Features & Use Cases

  • Final-outcome logging: write only the conclusive decision to history.md, discarding intermediate states.
  • Confirmation-driven writes: wait for explicit confirmation before recording changes.
  • Reversal handling: automatically update the history when a decision is reversed to reflect the true outcome.
  • Use Case: when a version decision moves from v0.6.0 to v0.8.17, the history entry records the final version and the reason.

Quick Start

Record the final decision 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
What is history hygiene in version documentation and decision logging?▼

History hygiene is the practice of recording only final, confirmed decisions to history.md to prevent intermediate drafts from polluting the decision trail and misleading future agents.

How do I log final outcomes to history.md without including intermediate drafts?▼

To log final outcomes to history.md, wait until a project decision is explicitly confirmed, then record only the conclusive result and the reason, discarding any intermediate states or requests.

Why does my team collaboration decision trail show reversed version changes?▼

Reversed decisions appear in the decision trail when intermediate states are logged. History hygiene requires immediately updating history.md to reflect only the true, final outcome when a reversal occurs.

Can I use history hygiene for project versioning remarks and feature changes?▼

Yes, history hygiene is applicable to project decisions, feature changes, and version remarks, ensuring that the single source of truth in your documentation reflects only the final, confirmed outcomes.

Do I need explicit confirmation before writing to a history log?▼

Yes, confirmation-driven writes are required. You must obtain explicit confirmation before recording changes to history.md to ensure disciplined logging and prevent unverified drafts from entering the decision trail.

What is the best way to maintain a single source of truth for team collaboration decisions?▼

The best way to maintain a single source of truth is to enforce history hygiene by writing only final, confirmed outcomes to history.md and immediately updating the record whenever a decision is reversed.

Related Skills

Explore More Content & Communication Skills→
robpitcherrobpitcher

history-hygiene

Record confirmed final outcomes to history.md after explicit confirmation.

Community
Intermediate
olivomarcoolivomarco
66

history-hygiene

Record confirmed final outcomes to history.md and update reversals immediately.

Community
Intermediate
Leep-GHLeep-GH

history-hygiene

Record final project outcomes in history.md with explicit confirmation.

Community
Intermediate
QuintenpsQuintenps

history-hygiene

Standardize project decision logs to record only final confirmed outcomes.

Community
Basic