commit
Commit
Use this skill whenever the user asks you to create a git commit for the current work.
Instructions
- Review the current git state before committing:
git statusgit diffgit log -5 --oneline
- Only stage files relevant to the requested change. Do not include unrelated untracked files, generated files, or likely-local artifacts.
- Always follow Ghost's commit conventions (see below) for commit messages
- Run
git status --shortafter committing and confirm the result.
Important
- Do not push to remote unless the user explicitly asks
- Keep commits focused and avoid bundling unrelated changes
- If there are no relevant changes, do not create an empty commit
- If hooks fail, fix the issue and create a new commit. Never bypass hooks.
More from tryghost/ghost
add admin api endpoint
Add a new endpoint or endpoints to Ghost's Admin API at `ghost/api/admin/**`.
84create database migration
Create a database migration to add a table, add columns to an existing table, add a setting, or otherwise change the schema of Ghost's MySQL database. Use this skill whenever the task involves modifying Ghost's database schema — including adding, removing, or renaming columns or tables, adding new settings, creating indexes, updating data, or any change that requires a migration file in ghost/core. Also use when the user references schema.js, knex-migrator, the migrations directory, or asks to "add a field" or "add a column" to any Ghost model/table. Even if the user frames it as a feature or Linear issue, if the implementation requires a schema change, this skill applies.
83format numbers
Format numbers using the formatNumber function from Shade whenever someone edits a TSX file.
45add-private-feature-flag
Use when adding a new private (developer experiments) feature flag to Ghost, including the backend registration and settings UI toggle.
1