remove-artifact-noise

Rewrites documents and code comments to remove conversational context and revision history.

2|Updated Sep 25, 2011
One-click install
npx skills add https://github.com/pokutuna/dotfiles --skill remove-artifact-noise-pokutuna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove-artifact-noise
Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/remove-artifact-noise
Command: npx skills add https://github.com/pokutuna/dotfiles --skill remove-artifact-noise-pokutuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents and code comments created through back-and-forth conversation often contain replies to the requester, abandoned plans, and phrasing that only makes sense with the original discussion context. This Skill rewrites such artifacts so readers who never saw the conversation can understand them as finished deliverables. ## Core Features & Use Cases - Conversation artifact removal: Deletes replies to the requester, change announcements, and shared-context shorthand, replacing them with self-contained statements. - Final-state normalization: Removes descriptions of abandoned approaches, stale TODO/FIXME markers, and inconsistent tone so the document reflects only the adopted outcome. - Rationale preservation: Keeps the history of the subject itself, such as design decisions, trade-offs, and constraints, while removing the history of how the artifact was produced. - Use Case: After drafting a design doc through an AI chat session, run this Skill to strip out phrases like "as you requested" and "we changed the approach", leaving a clean document ready for teammates. ## Quick Start Review this document and rewrite it so a reader who never saw our conversation can understand it as a finished deliverable.

Frequently Asked Questions about remove-artifact-noise

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

FAQPage Schema
How do I clean up AI-generated documents before sharing them?

Remove conversational artifacts like replies to the requester, change announcements, and shorthand that only makes sense in the original chat. Rewrite the document so it reads as a finished deliverable understandable without the production context.

How to remove revision history noise from technical documentation?

Delete descriptions of abandoned approaches, phrases like "initially" or "changed from the previous version", and leftover TODO markers. Align the entire document with the final adopted content and unify tone and terminology across sections.

Should design rationale be removed when cleaning up documents?

No. The subject's own history, such as design decisions, alternatives considered, constraints, and trade-offs, should be preserved. Only the artifact's production history, like the order in which ideas were discussed in conversation, is removed.

When should I not rewrite a document for clarity?

Do not force changes when nothing needs fixing; state briefly why no edits were made. Also avoid deleting intentionally deferred decisions, and do not shorten text at the cost of making readers guess at meaning.

Can this approach edit files directly or only suggest changes?

It rewrites the target text directly, editing files in place when the target is a file. When changes are requested as a proposal, it presents each fix in before-and-after form instead.