Menu
Format changelog content according to Replit's changelog template structure. Use when converting raw changelog content into properly structured documentation with correct frontmatter, sections, and media formatting.
Write content following Replit's brand voice and style guidelines. Use when creating or reviewing any user-facing content including changelogs, documentation, or marketing materials. Ensures consistent professional yet approachable tone.
Review and improve documentation quality using best practices. Use when reviewing changelogs, documentation, or any written content to ensure clarity, accuracy, and helpfulness.
Insert images and videos from Slack messages into changelog markdown. Use when you have media files downloaded from Slack that need to be included in documentation.
| name | changelog-formatting |
| description | Format changelog content according to Replit's changelog template structure. Use when converting raw changelog content into properly structured documentation with correct frontmatter, sections, and media formatting. |
| targets | ["*"] |
This skill helps you format changelog content according to Replit's template structure.
Convert raw changelog content into properly structured documentation following:
Use the add_changelog_frontmatter tool - don't write frontmatter manually:
# The tool will create:
---
title: October 30, 2025
description: 2 min read
---
Immediately after frontmatter, add a "## What's new" section with anchor-linked bullet points for ALL updates (both Platform and Teams/Enterprise):
## What's new
* [Feature One](#feature-one)
* [Feature Two](#feature-two)
* [Enterprise Feature](#enterprise-feature)
Anchor format: Convert feature name to lowercase, replace spaces with hyphens.
After the TOC, organize content into two main sections:
Each section should have ### subsections for each feature:
## Platform
### Feature One
Description of the feature.
### Feature Two
Description of the feature.
## Teams and Enterprise
### Enterprise Feature
Description of the feature.
Process for each media reference:
Verify the file exists first:
./docs/updates/media/YYYY-MM-DD/filename exists on the filesystemConvert local paths to public CDN paths:
./media/YYYY-MM-DD/filename → /images/changelog/YYYY-MM-DD/filename
Wrap in <Frame> tags with proper syntax:
For Images (.png, .jpg, .jpeg, .gif, .webp):
<Frame>
<img src="/images/changelog/2025-01-15/feature.png" alt="Descriptive alt text" />
</Frame>
For Videos (.mp4, .mov, .webm):
<Frame>
<video src="/images/changelog/2025-01-15/demo.mp4" controls />
</Frame>
Preserve descriptive alt text from the original markdown
Common Path Mistakes:
./media/2025-01-15/file.png (local path - wrong in final output)./docs/updates/media/2025-01-15/file.png (full local path - wrong)/media/2025-01-15/file.png (missing "images/changelog" - wrong)/images/changelog/2025-01-15/file.png (correct CDN path)CRITICAL: Remove all Slack announcement links from the final output. These are for internal tracking only and should not appear in the published changelog.
Remove lines like:
[Slack announcement](https://replit.slack.com/archives/...)
<!-- slack_timestamps: 123,456,789 -->
# Changelog: January 15, 2025
## Updates for this week
We shipped a new dashboard!
Also fixed some bugs in the editor.
[Slack announcement](https://replit.slack.com/archives/C123/p456)
### SAML improvements
SSO setup is now easier with better error messages.
[Slack announcement](https://replit.slack.com/archives/C123/p789)
<!-- slack_timestamps: 123,456,789 -->
---
title: January 15, 2025
description: 2 min read
---
## What's new
* [New dashboard](#new-dashboard)
* [Editor bug fixes](#editor-bug-fixes)
* [SAML improvements](#saml-improvements)
## Platform
### New dashboard
<Frame>
<img src="/images/changelog/2025-01-15/dashboard.png" alt="New dashboard interface" />
</Frame>
We shipped a new dashboard with improved metrics visibility.
### Editor bug fixes
Fixed several bugs in the editor for a smoother experience.
## Teams and Enterprise
### SAML improvements
SSO setup is now easier with better error messages.
Input with reference to non-existent file:
### Feature X
Description of feature X.
Output (missing file removed):
### Feature X
Description of feature X.
Before completing the formatting task, verify:
add_changelog_frontmatter tool (not manually written)# Changelog:...)### headings under their respective sections---) between sections* for bullets (not - or +)* [Feature Name](#feature-name)<Frame> tags<Frame><img src="..." alt="..." /></Frame><Frame><video src="..." controls /></Frame>/images/changelog/YYYY-MM-DD/filename)