scar-tissue

Removes superseded residue from artifacts after corrections, migrations, and diagnostic tests.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill scar-tissue-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scar-tissue
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/house-rules/skills/scar-tissue
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill scar-tissue-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Corrective work, migrations, and temporary diagnostic tests often leave behind superseded layers: outdated prose, obsolete tests, migration wrappers without consumers, and worklog narration embedded in living documents. This Skill identifies and removes that residue so artifacts reflect only their current responsibility. ## Core Features & Use Cases - Residue Detection: Distinguishes scar tissue (superseded layers, worklog narration, retired interpretations) from load-bearing guards, compatibility paths, and published history. - Living Document Cleanup: Rewrites READMEs, runbooks, and instruction files around present-tense identity, removing origin SHAs, former names, and lineage that Git already owns. - Diagnostic Stitch Resolution: Evaluates temporary tests introduced during repair, keeping or rewriting them as positive specifications and removing those that only prove a retired interpretation. - Use Case: After a migration, a service README still mentions the old repository and import SHA. Invoke the skill to rewrite the README around the current service identity while preserving the separate import audit that legitimately records lineage. ## Quick Start Ask the agent to review the current artifact for scar tissue and remove superseded layers before handoff.

Frequently Asked Questions about scar-tissue

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

FAQPage Schema
How do I clean up residue after a code migration?▼

Inspect the affected artifacts for old and new intentions surviving together, then consolidate them into the form they would have had if the final decision were known at the start. End the migration with one canonical implementation and avoid inventing forwarding paths without a named current consumer.

What is scar tissue in code and documentation?▼

Scar tissue is residue from the fixing process rather than structure the current system needs: corrections layered over superseded content, temporary tests whose subject is gone, migration wrappers without consumers, or prose narrating the struggle instead of the result.

When should I remove a temporary diagnostic test?▼

Remove a diagnostic stitch during the Refactor phase when positive coverage already owns the intended behavior. Verify by temporarily reverting the fix to confirm the surviving specification fails, then restore the fix and confirm it passes.

Should a README mention the old repository after a migration?▼

No. A living README introduces the artifact as it exists now; origin repositories, import SHAs, and former names are historical residue that Git already tracks. Only an explicit audit or migration record should retain that lineage.

When should cleanup history be preserved instead of removed?▼

Preserve history when an external reader depends on it, such as published changelogs, released documentation, pushed commits, decision records, or audits whose current responsibility is carrying historical evidence.