Release notes

Turns commits into notes a customer can read.

Engineering · produces a Document · built in, ready to run

What you give it

Something like this:

- feat(order): add offline queue, flush on reconnect
- feat(i18n): urdu labels for order + cart screens
- fix(import): handle quoted commas in price list CSV
- fix(sap): correct field mapping for tax_code, was sending null
- perf(order-list): add index on orders.store_id, list query 2.4s -> 180ms
- chore: bump laravel to 11.9
- fix(auth): session no longer dropped when switching stores
- feat(rep): reps now see portal-placed orders in their own list

What you get back

This is a real run of the skill on the input above, not a mock-up:

Let me provide the release notes directly:

---

# Release Notes

## New

**Your orders now work offline**  
Place and edit orders without an internet connection. Changes sync automatically when you reconnect.

**Urdu language support**  
Order and cart screens now display in Urdu for better usability in your region.

**Sales reps see all their orders**  
Orders placed through the customer portal now appear in your rep list, giving you a complete view of all activity.

## Improved

**Order list loads instantly**  
Searching and filtering your orders is now 13× faster — from 2.4 seconds to 180 milliseconds.

**Switching stores keeps you logged in**  
No more dropping your session when moving between store locations. Stay in the system without re-authenticating.

## Fixed

- **CSV imports now handle special characters**  
Quoted commas in price lists import correctly without errors.

- **Tax codes sync properly to SAP**  
Tax information now exports accurately to your ERP system instead of sending empty values.

---

**Key impact:** Offline reliability, performance gains, and language support. Left out internal dependency updates (Laravel bump) and code refactors.

The wording changes a little every run. The shape does not — that is what the procedure below is for.

Tools it uses

None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.

The procedure it follows

This is the skill, in full. Add it to your own skills to change any of it.

Write release notes from the changes below.

Group as: New, Improved, Fixed. Within each, order by how much a user would care.

Write for the person using the product, not the person who wrote the code — "you can now export to CSV", not "added CsvExportService". Leave out refactors and internal changes nobody will notice.

How to run it

In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.

New to skills? Start with what a skill is.