Agent skill

History Hygiene

by FritzAndFriends in FritzAndFriends/SharpSite

Record final outcomes to history.md, not intermediate requests or reversed decisions

MITAuto-check passed

Install History Hygiene

skills CLI
$ npx skills add FritzAndFriends/SharpSite --skill history-hygiene -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FritzAndFriends/SharpSite history-hygiene --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FritzAndFriends/SharpSite.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.copilot/skills/history-hygiene .claude/skills/history-hygiene && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
history-hygiene
GitHub stars
145
Used in
1 other repo
Token cost
~396 tokens
SKILL.md length
178 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Record final outcomes to history.md, not intermediate requests or reversed decisions

  • SKILL.md covers Context, Patterns, Examples and Anti-Patterns
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

History Hygiene is an agent skill from FritzAndFriends/SharpSite. Record final outcomes to history.md, not intermediate requests or reversed decisions

Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A basic CMS built with .NET 9 and Blazor. The licence is MIT.

Example prompts

  • “/history-hygiene”

What it can do on your machine

Read from SKILL.md and the folder at commit c35e5e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

History Hygiene loads about 396 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 178 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~396

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FritzAndFriends/SharpSite at commit c35e5e0, republished under its MIT licence (© FritzAndFriends). 178 words, ~396 tokens.

Download SKILL.mdSave it as .claude/skills/history-hygiene/SKILL.md (or your agent's skills folder).
name
history-hygiene
description
Record final outcomes to history.md, not intermediate requests or reversed decisions
domain
documentation, team-collaboration
confidence
high
source
earned (Kobayashi v0.6.0 incident, team intervention)

Context

History files (.md files tracking decisions, spawns, outcomes) are read cold by future agents. Stale or incorrect entries poison decision-making downstream. The Kobayashi incident proved this: history said "Brady decided v0.6.0" when Brady had reversed that to v0.8.17. Future spawns read the wrong truth and repeated the mistake.

Patterns

  • Record the final outcome, not the initial request.
  • Wait for confirmation before writing to history — don't log intermediate states.
  • If a decision reverses, update the entry immediately — don't leave stale data.
  • One read = one truth. A future agent should never need to cross-reference other files to understand what actually happened.

Examples

✓ Correct:

  • "Migration target: v0.8.17 (initially discussed as v0.6.0, corrected by Brady)"
  • "Reverted to Node 18 per Brady's explicit request on 2024-01-15"

✗ Incorrect:

  • "Brady directed v0.6.0" (when later reversed)
  • Recording what was requested instead of what actually happened
  • Logging entries before outcome is confirmed

Anti-Patterns

  • Writing intermediate or "for now" states to disk
  • Attributing decisions without confirming final direction
  • Treating history like a draft — history is the source of truth
  • Assuming readers will cross-reference or verify; they won't

© FritzAndFriends, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .copilot/skills/history-hygiene of FritzAndFriends/SharpSite.

Open the folder on GitHubat commit c35e5e0

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in FritzAndFriends/SharpSite, which our catalogue first saw on October 7, 2026.

Compare with similar skills

History Hygiene next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

History Hygiene compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
History Hygiene this skillFritzAndFriends/SharpSite1451 repos~396Automated safety check: PassMIT
History Hygienebradygaster/squad3.3k—~475Automated safety check: PassMIT
Recordingcodewhale-hq/Codewhale41k—~540Automated safety check: PassMIT
Architecture Decision Recordsaffaan-m/ECC277k4 repos~1.8kAutomated safety check: PassMIT
Architecture Decision Recordsaffaan-m/ECC277k1 repos~863Automated safety check: PassMIT
Architecture Decision Recordsaffaan-m/ECC276k—~1.1kAutomated safety check: PassMIT

Similar skills

  • History Hygiene

    bradygaster/squad

    Record reconciled final outcomes to history.md, not intermediate requests or obsolete claims

    3.3k GitHub stars~475 tokensUpdated yesterday
    Auto-check passed
  • Recording

    codewhale-hq/Codewhale

    Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures.

    41k GitHub stars~540 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.

    277k GitHub starsUsed in 4 repos~1.8k tokens
    DevelopmentAuto-check passed
  • 在Claude Code会话期间,将做出的架构决策捕获为结构化的架构决策记录(ADR)。自动检测决策时刻,记录上下文、考虑的替代方案和理由。维护一个ADR日志,以便未来的开发人员理解代码库为何以当前方式构建。

    277k GitHub starsUsed in 1 repo~863 tokens
    DevelopmentAuto-check passed
  • コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。

    276k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Browser Record

    ruvnet/ruflo

    Open a named, traced browser session into an RVF cognitive container with a ruvector trajectory recording every action

    74k GitHub stars~735 tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

More from FritzAndFriends/SharpSite

All 18 skills in this repo
  • Architectural Proposals

    FritzAndFriends/SharpSite

    How to write comprehensive architectural proposals that drive alignment before code is written

    145 GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed
  • Client Compatibility

    FritzAndFriends/SharpSite

    Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces

    145 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Distributed Mesh

    FritzAndFriends/SharpSite

    How to coordinate with squads on different machines using git as transport

    145 GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed
  • Docs Standards

    FritzAndFriends/SharpSite

    Microsoft Style Guide + Squad-specific documentation patterns

    145 GitHub starsUsed in 2 repos~567 tokens
    Auto-check passed
  • Economy Mode

    FritzAndFriends/SharpSite

    Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.

    145 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • External Comms

    FritzAndFriends/SharpSite

    PAO workflow for scanning, drafting, and presenting community responses with human review gate

    145 GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

Questions about History Hygiene

What does History Hygiene do?

Record final outcomes to history.md, not intermediate requests or reversed decisions. History Hygiene is an agent skill from FritzAndFriends/SharpSite.

How do I install History Hygiene in Claude Code?

Run `npx skills add FritzAndFriends/SharpSite --skill history-hygiene -a claude-code`. Or copy the skill folder (.copilot/skills/history-hygiene in FritzAndFriends/SharpSite) into .claude/skills/history-hygiene in your project. Claude Code loads it when a task matches its description.

How do I install History Hygiene in Codex?

Run `npx skills add FritzAndFriends/SharpSite --skill history-hygiene -a codex`. Or copy the skill folder (.copilot/skills/history-hygiene in FritzAndFriends/SharpSite) into .agents/skills/history-hygiene in your project. Codex loads it when a task matches its description.

Can I use History Hygiene in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FritzAndFriends/SharpSite --skill history-hygiene -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/history-hygiene, .gemini/skills/history-hygiene, .github/skills/history-hygiene and .opencode/skills/history-hygiene in your project.

What does History Hygiene need to run?

SKILL.md names no scripts, command-line tools or credentials: History Hygiene is instructions for the agent only.

Does History Hygiene access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is History Hygiene safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does History Hygiene use?

History Hygiene is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does History Hygiene use?

About 396 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to History Hygiene?

Skills that share tags, products or a category with History Hygiene: History Hygiene (bradygaster/squad, 3.3k stars), Recording (codewhale-hq/Codewhale, 41k stars), Architecture Decision Records (affaan-m/ECC, 277k stars) and Architecture Decision Records (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains History Hygiene?

FritzAndFriends (a GitHub organization) maintains it in FritzAndFriends/SharpSite, which has 145 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on April 30, 2026.

Source: FritzAndFriends/SharpSite on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.