Files
skillshare/website/docs/reference/commands/commit.md
T
2026-05-27 17:03:13 +08:00

71 lines
1.7 KiB
Markdown

---
sidebar_position: 1
---
# commit
Create a local git commit for source skills without pushing.
```bash
skillshare commit # Commit with default message
skillshare commit -m "Update skill" # Custom message
skillshare commit --dry-run # Preview
```
## When to Use
- Save a local checkpoint before experimenting with skill edits
- Commit changes on a machine or source repo that does not have a remote configured
- Keep local history separate from sharing changes across machines
Use [`push`](./push.md) when you want to commit **and** push to a git remote.
## What Happens
```mermaid
flowchart TD
CMD["skillshare commit"]
CHECK["1. Check repository status"]
STAGE["2. Stage all changes"]
COMMIT["3. Commit"]
CMD --> CHECK --> STAGE --> COMMIT
```
`commit` stages all changes in the skills source directory and creates a git commit. It does not require a remote and never runs `git push`.
## Options
| Flag | Description |
|------|-------------|
| `-m, --message <msg>` | Commit message (default: "Update skills") |
| `--dry-run, -n` | Preview without making changes |
## Prerequisites
Your skills source directory must be a git repository:
```bash
skillshare init
```
If the source is not a git repository, `commit` prints a setup hint and exits without changing files.
## Examples
```bash
# Commit with the default message
skillshare commit
# Commit with a custom message
skillshare commit -m "Update review skill"
# Preview staged files and message without committing
skillshare commit --dry-run
```
## See Also
- [push](./push.md) — Commit and push to a git remote
- [pull](./pull.md) — Pull from remote and sync to targets
- [status](./status.md) — Check git and sync state