When to use
Use when there is a need to clean up "this change", "the reviewer believes", "the previous version", unsubmitted design numbers, or other text that cannot be resolved in the current repository context.
Execution flow
- Clarify the file scope, language pairing, and whether modification is allowed.
- Distinguish current facts, contracts, historical records, reasoning processes, and review conversations.
- Delete purely process-related content; rewrite valuable facts as current-state statements.
- Preserve negative guarantees, measurement boundaries, formal citations, archived records, and fixture fidelity.
Core constraints
- Do not rewrite assumptions as implemented capabilities.
- Do not modify sealed archives, record-type fixtures, or generated files unless the user explicitly authorizes it.
- Bilingual files must remain semantically synchronized.
Read before producing prompts/skill-prose-trim.md。