---
name: ship-to-production
description: Ship changes to production with full documentation: commits, push, deployment, and automatic changelog updates.
---

# Ship to Production with Documentation

## 1. What it does
Formalizes the process of shipping changes to production: commits, pushes, deploys to the hosting platform, and updates the changelog automatically. Always confirms first that the necessary tests and reviews are already complete.

## 2. When to use it
- Finishing a feature that's ready for production
- Needing a clear record of what was shipped and when
- Coordinating frequent deployments with a team

## 3. Steps
1. Confirm prior tests and reviews are complete
2. Review and commit any pending changes
3. Push the changes to the main branch
4. Deploy to the configured hosting platform
5. Update the changelog with a summary of the change
6. Confirm with the client that the deployment completed successfully

## 4. GoHighLevel angle
If the deployment affects a GoHighLevel snapshot or funnel, confirm the snapshot is up to date before announcing the change to the client.

## 5. Safety rules
Always work in draft mode: nothing is sent, published, or paid for without explicit client approval. Never invent data, metrics, or results. No passwords, tokens, or API keys are requested or shown in chat.

## 6. Deliverable
A clear, reviewable draft of the output (text, code, report, or file), ready for the user to approve before it becomes final.