history-hygiene

Name: history-hygiene
Availability: InStock
Author: mpaulosky

Record only confirmed final outcomes in history.md and decision logs.

Updated Mar 18, 2022

Search Tags:#documentation #history #team-collaboration #audit-trail #change-management #decision-log #agent-hygiene

Ready to run

npx skills add https://github.com/mpaulosky/dotfiles --skill history-hygiene-mpaulosky

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

History-hygiene prevents downstream agents and team members from acting on stale, intermediate, or reversed decisions by ensuring history.md and similar records only contain final, confirmed outcomes and accurate attributions.

Core Features & Use Cases

Final-outcome recording: Write only confirmed results to history files, not interim requests or tentative states.
Reversal handling: Update entries immediately when decisions are reversed to avoid leaving stale truths.
Confirmation gating: Require explicit confirmation before persisting records so accidental or premature logs are avoided.
Use Case: During release coordination, record the final chosen version and the reason, rather than initial proposals that were later abandoned.

Quick Start

Ask the AI to update history.md with the confirmed final outcome, include the author and timestamp, and correct any prior stale entries.

Frequently Asked Questions about history-hygiene

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

FAQPage Schema

How do I prevent stale entries from misleading downstream agents reading my decision log?▼

Prevent stale entries in a decision log by requiring explicit confirmation before any file writes, ensuring only final confirmed outcomes are recorded rather than intermediate requests or reversed decisions.

What is the best way to manage history.md files during release coordination?▼

Manage history.md during release coordination by recording only the final chosen version and the reason, while immediately updating or correcting any prior stale entries to maintain a single source of truth.

How do I update changelogs when a decision is reversed?▼

Update changelogs on reversal by immediately modifying the existing entry to reflect the final outcome, preventing downstream automation from acting on abandoned proposals or inaccurate attributions.

Why do my deployment notes contain intermediate requests instead of final outcomes?▼

Deployment notes contain intermediate requests when history files are written prematurely without confirmation gating, which can be fixed by requiring explicit confirmation before persisting records.

Can I use atomic file operations to ensure consistent history logs for team collaboration?▼

Yes, use atomic single-truth file operations to ensure downstream agents read a consistent source of truth, preventing partial updates or race conditions from corrupting team history records.

When do I need confirmation gating for writing spawn records?▼

You need confirmation gating for writing spawn records whenever stale entries could mislead future automation, requiring explicit confirmation before persisting to avoid accidental or premature logs.