deslop-history

Remove historical commentary from ADRs while preserving current decisions and constraints.

1|Updated Apr 13, 2026

Search Tags:#documentation #cleanup #artifact #adrs #decision-notes #content-editing

Ready to run

npx skills add https://github.com/t-uda/skills --skill deslop-history

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deslop-history
Source: https://github.com/t-uda/skills/tree/main/skills/deslop-history
Command: npx skills add https://github.com/t-uda/skills --skill deslop-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean up final artifacts derived from decisions by removing historical noise while preserving critical decisions, constraints, and rationale needed for future work.

Core Features & Use Cases

Preserve current decisions and operational boundaries while removing historical commentary and draft notes.
Automate the transformation of artifact drafts into user-facing final forms for handoffs and audits.
Use case: You have an ADR-like decision note with draft discussions; run this skill to produce a concise final artifact for stakeholders and engineers.

Quick Start

Run the deslop-history tool on the latest artifact to produce the final user-facing version.

Frequently Asked Questions about deslop-history

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

FAQPage Schema

How do I remove draft discussion notes from ADRs for stakeholder handoffs?▼

To remove draft discussion notes from ADRs, the tool identifies and strips historical commentary while preserving current decisions, constraints, and operational rationale to produce a clean final artifact.

What is the best way to clean up decision notes for audits?▼

Cleaning up decision notes for audits is best handled by enforcing present-state phrasing and removing legacy commentary, which ensures the artifact remains stakeholder-ready and retains critical compatibility boundaries.

Does cleaning historical context from artifact drafts delete compatibility notes?▼

No, cleaning historical context from artifact drafts does not delete compatibility notes. The process specifically preserves required compatibility notes and operational boundaries while eliminating nonessential historical context.

How do I rewrite artifact content to use present-state phrasing?▼

You can rewrite artifact content to present-state phrasing by running the deslop-history tool, which automatically transforms drafts by removing historical noise and updating the language to reflect the current state.

When should I not use automated content-editing to clean final artifacts?▼

You should avoid automated content-editing for final artifacts when the legacy commentary itself contains critical operational rationale that cannot be separated from the historical context, though the tool attempts to preserve rationale.