Create swarm-safe git checkpoints with locking, validation, and strict commits.
npx skills add https://github.com/corygabrielsen/skills --skill checkpoint-corygabrielsen
Please help me install this Agent Skill. Skill: checkpoint Source: https://github.com/corygabrielsen/skills/tree/main/checkpoint Command: npx skills add https://github.com/corygabrielsen/skills --skill checkpoint-corygabrielsen
This Skill enables teams to create safe, repeatable checkpoints in any Git repository. It locks access to prevent concurrent edits, captures a clean snapshot of the working tree, and enforces explicit staging and commit rules to avoid accidental data loss or messy history.
Run the checkpoint skill to create a swarm-safe snapshot of the current repository. The workflow acquires a local lock, validates the working tree, prompts for explicit file selection, creates a commit with a strict subject/body, and optionally pushes to the remote.
High-intent search queries and answers about installing and using this skill.
Safe git commits in a multi-agent environment require atomic locking and explicit staging to prevent concurrent collisions. This skill acquires a repository-local lock, validates the working tree, and stages only selected files before committing.
A swarm-safe git checkpoint is a deterministic snapshot that locks the repository, captures status and diffs, and enforces strict commit-message formatting. It prevents accidental data loss and messy history in multi-agent development workflows.
Enforcing a strict commit-message format during staging requires a validation step before finalizing the commit. This skill enforces conventional, well-formed commit messages with a strict subject and body while explicitly staging only selected files.
Yes, you can automatically push commits to a remote repository after creating a checkpoint. This skill supports optional push behavior, releasing the repository-local lock only after the push operation completes successfully.
Preventing concurrent edits and data loss requires atomic locking and clean snapshot validation before committing. This approach locks access to prevent collisions, captures the working tree status, and enforces explicit staging rules.
Yes, this git checkpointing approach works without additional dependencies or external tools. It operates independently within any repository to handle locking, status capture, and precise file staging in multi-agent environments.
brianpunzalanDetect the GitHub owner and repository from a local Git remote URL.
Fandry96Stage changes, generate conventional commits, and push to a remote Git repository.
dorrioConfigure Husky, lint-staged, commitlint, and Python pre-commit hooks.
angelgarciasolorzanoManage git repositories through a text-based CLI for commits, branches, and staging.
