Auto-Cleanup Approaches

Iteration markers (%% %%, •%%> <%%•, ==text(TOKEN)==) are meant for drafting - they shouldn’t end up in final documents. This section covers different approaches to catch and remove markers before they’re committed or published.

Why Auto-Cleanup?

Manual cleanup works, but it’s easy to forget. Auto-cleanup provides safety nets:

• Catch forgotten markers before they reach git
• Enforce consistency across team members
• Reduce friction by automating the obvious

Approaches

Choose based on your workflow:

Approach	When it runs	Requires Claude	Best for
Claude Check	Before commit (manual)	Yes	Claude Code users
Git Hooks	On git commit	No	Solo developers
CI/CD Check	On push/PR	No	Teams
Editor Integration	While editing	No	Visual feedback
Lint Rules	On lint/save	No	Existing lint setup

Recommendations

Using Claude Code? Start with Claude Check - it’s built into the skill workflow.

Working in a team? Add CI/CD Check as a backup - catches anything that slips through locally.

Want prevention over detection? Use Editor Integration to see markers visually while editing.

Combining Approaches

These aren’t mutually exclusive. A robust setup might use:

1. Editor integration - See markers while writing
2. Claude check - Catch before commit
3. CI/CD - Final safety net

Related

• Customization - Configure cleanup behavior
• Cleanup Syntax - Manual cleanup commands