change-headings_skill

Overview

This skill converts all headings in a document into standard paragraphs while preserving their original visual appearance. It flattens heading elements but keeps font size, weight, color, alignment, and inline formatting intact. The result is uniform paragraph styling that looks identical to the original headings.

How this skill works

The skill scans the document for heading elements (Heading 1–6), captures each heading's visual attributes and inline formatting, and replaces the heading element with a normal paragraph element. Captured attributes — font size, weight, color, alignment, bold/italic/underline, links and other inline styles — are reapplied to the paragraph so the appearance remains unchanged. It also preserves surrounding spacing, lists, indentation, and document order while ensuring no heading styles remain.

When to use it

• Preparing documents for systems that don't support semantic headings but must keep the same look
• Standardizing text styles before exporting to formats or tools that strip heading semantics
• Cleaning files for print or layout workflows where headings cause unwanted automatic behaviors
• Removing heading-based formatting for content migration while maintaining visual fidelity
• Ensuring visual consistency when automated heading styles break layout or templates

Best practices

• Run a quick backup of the original document before conversion
• Verify inline elements like links and annotations remain clickable after conversion
• Check list and table contexts where headings might affect flow or numbering
• Confirm paragraph spacing and indentation match expected layout after conversion
• Test on a sample document when integrating into automated pipelines

Example use cases

• Convert a multi-level technical spec so all headings become paragraphs but keep the same sizes and boldness for print-ready output
• Normalize a marketing brochure that used heading styles causing template overrides in the CMS
• Prepare an academic paper for a publisher that requires no semantic headings but preserved typography
• Migrate content to a platform that strips heading tags while maintaining the original look
• Flatten headings in a collaborative doc before exporting to a tool that misinterprets heading structure