Changelog Skill
Transform completed Linear issues/projects into customer-facing changelog entries for Featurebase.
Prerequisites
FEATUREBASE_API_KEYinformica/.env- Linear MCP tools available
Quick Commands
# List existing changelogs
php formica/scripts/featurebaseHandler.php list --limit=10
# Get a specific changelog by ID
php formica/scripts/featurebaseHandler.php get <id>
# Create draft
php formica/scripts/featurebaseHandler.php create "Title" --md=/tmp/changelog.md --categories=New
# Update existing changelog
php formica/scripts/featurebaseHandler.php update <id> --md=/tmp/changelog.md --categories=Improved
# Get help
php formica/scripts/featurebaseHandler.php help
Featurebase Categories
| Category | When to Use |
|---|---|
New | New features, new functionality |
Improved | Enhancements, optimizations, performance |
Fixed | Bug fixes |
Linear Label Mapping
| Linear Label | → Featurebase Category |
|---|---|
feature, enhancement, new | New |
improvement, optimization, performance | Improved |
bug, fix, bugfix | Fixed |
Content Templates
New Feature
**TL;DR:** [One-line summary of what users can now do]
## What's new?
[2-3 sentences explaining the feature and its benefit]
## How it works
- **[Key concept 1]:** [Brief explanation]
- **[Key concept 2]:** [Brief explanation]
💡 **Result:** [Main benefit for the user]
➡️ [**Learn more**](https://help.publica.la/...)
Improvement
**[Bold intro explaining what changed and why it matters]**
[1-2 paragraphs of context]
### What's changing?
- **[Change 1]:** [Description]
- **[Change 2]:** [Description]
**Access from:** Dashboard → [Path to feature]
Bug Fix
**[Brief description of what was fixed]**
[Context about the issue and resolution]
- **Issue:** [What was happening]
- **Resolution:** [What we fixed]
This fix is now live for all stores.
Languages
Every changelog entry MUST include all 3 languages in a single content block, in this order:
- 🇪🇸 Español — Neutral Spanish (no regional variants: no voseo, no argentinisms, no Spain-specific terms)
- 🇺🇸 English — American English (US spelling: "customize" not "customise", "color" not "colour")
- 🇧🇷 Português — Brazilian Portuguese (pt-BR, not pt-PT)
Each language section is separated by --- (horizontal rule).
Language headers
Each language section MUST start with a flag heading for easy identification:
- Spanish section:
# 🇪🇸 [Title in Spanish] - English section:
# 🇺🇸 [Title in English] - Portuguese section:
# 🇧🇷 [Title in Portuguese]
This makes it easy to visually scan where each language starts when reviewing the draft.
Style Guide
| Element | Guideline |
|---|---|
| Tone | Professional but friendly |
| Bold | Key concepts, feature names |
| Emojis | Sparingly: 💡 ➡️ 🔗 |
| Links | Help center when relevant |
| Length | 100-300 words per language |
Example Changelogs (Reference)
Good New Feature
**A direct, frictionless buying experience—perfect for campaigns, promotions, and more.**
Selling your publications or subscription plans is now simpler than ever. With **Automatic Checkout**, users can go straight to payment from a single link, with no extra steps.
## How it works
- **Smart detection:** The system checks if the user is logged in and takes the right action
- **Direct links:** Create URLs that skip the catalog and go straight to checkout
- **Preserved intent:** Even if login is required, the purchase intent is saved
💡 **Result:** Higher conversions and a smoother buying experience.
➡️ [**Learn how to set up Automatic Checkout**](https://help.publica.la/...)
Good Improvement
**Choose which transactional emails are sent from Publica.la and which ones you manage externally.**
Administrators can now **enable or disable individual email notifications**—such as registration emails, purchase confirmations, or shipping updates—directly from the dashboard.
This update lets you integrate external platforms (like Braze, Customer.io, or custom systems) **without duplicating notifications**.
**Access from:** Dashboard → Settings → Notifications
Output
The skill creates a draft only. Publication is manual via Featurebase dashboard.
IMPORTANT: Never publish or send email notifications from the CLI. Always use --email = false (the default). Email notifications are only sent manually from the Featurebase dashboard after review.