Skip to content
Skills Library
Programming · Automation

gitly-save

/gitly-save

Review project changes and save an intentional version with a meaningful commit. Use for save/commit requests such as "save everything I did today", "save my progress", "שמור", or "שמור את ההתקדמות".

Repository
vibe.md ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Review project changes and save an intentional version with a meaningful commit. Use for save/commit requests such as "save everything I did today", "save my progress", "שמור", or "שמור את ההתקדמות".

Triggers from the description

save everything I did todaysave my progressשמורשמור את ההתקדמות
Original author description

Review project changes and save an intentional version with a meaningful commit. Use for save/commit requests such as "save everything I did today", "save my progress", "שמור", or "שמור את ההתקדמות".

How it works

  1. Responsibility and triggers
  2. Prerequisites and inspection
  3. Mutating workflow
  4. Output, errors, and recovery
Original SKILL.md headings · 30 lines, 337 words
SKILL.md preview
---
name: gitly-save
description: Review project changes and save an intentional version with a meaningful commit. Use for save/commit requests such as "save everything I did today", "save my progress", "שמור", or "שמור את ההתקדמות".
license: MIT
metadata:
  collection: vibe.md
  group: gitly
  source: https://github.com/vibe-md/vibe.md
  upstream: https://github.com/NirGeron98/Gitly
  upstream-commit: fe33bbae13552ed8973c6949b1d21e1ce2b746c9
---

# Gitly save

Read [the shared operating contract](../GITLY.md) first and follow its approval contract.

## Responsibility and triggers

Create one truthful local version from an explicitly reviewed set of changes. Examples: “Save my progress,” “save only the login fix,” “commit this,” “שמור את כל מה שעשיתי היום”. Use `gitly-setup` when Git or identity is missing and `gitly-sync` only for an explicitly requested/configured online backup.

## Prerequisites and inspection

Read preferences, then inspect branch/HEAD, full status, staged changes, untracked and ignored paths, and relevant diffs. Detect likely secrets by filename and content patterns without printing values. Flag large files, generated output, binaries, submodules, LFS candidates, and changes that cannot be understood from the diff. Never use `git add .` or `git add -A`.

Existing staged paths are part of the proposed commit. If any are outside the intended save, stop and ask whether to include them or handle them separately; do not silently unstage them.

## Mutating workflow

Create an evidence-backed, concise commit subject in the user's language unless project conventions require another language. The plan must list every path, existing staged content, the exact message, whether hooks can run, and whether a later GitHub backup is proposed. After approval and a fresh state check:

1. Stage only each approved path with `git add -- <paths>`.
2. Verify `git diff --cached --name-status` and `git diff --cached --check` exactly match the plan.
3. Commit with the approved message.
4. Verify the new commit ID and that unapproved working changes remain.

If `save_destination` is `local_and_github`, coordinate with `gitly-sync`. A separate sync plan/approval is the safe default; a combined approval is valid only when both exact steps and remote effects were shown up front.

## Output, errors, and recovery

Report what was saved, what remains unsaved, the readable description, date, and short commit ID as secondary metadata. Stop on no changes, missing identity, secret uncertainty, ignored files, changed state, hook failure, index mismatch, detached HEAD, or commit failure. A local commit is recoverable through `gitly-restore`; never amend or rewrite it silently.

Versions

The database has no other skills named gitly-save.

Database snapshot: 13.11.2026 · package version 180b676f9e04 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100smart-git-workflow-copilot
    Provides interactive planning and strategic workflow design for branching, commit scoping, and logical task segmentation. Use this skill when planning how to organize work before executing actions with gitly-save, gitly-branches, or gitly-sync.
  • 100gitly-setup
    Check Git readiness and safely prepare a project repository. Use for Gitly setup, initialization, Git identity, ignore-file, "set up Git", "הגדר גיט", or "אתחל מאגר" requests.
  • 100git-commit
    Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
  • 100git-commit
    Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
  • 90review
    Review uncommitted changes against the project rules before committing. Use when the user asks for a review of their working tree, asks whether changes are ready to commit, or says they are about to commit.
  • 92commit
    [Git] Use when asked to commit, stage and commit, or save changes. --push also pushes.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.