skills.rest
pelchers
pelchersCOMMUNITY
Explore all skills by this author →
GitHub

savepoint-branching

Create and push savepoint branches from the current commit state.

Updated Mar 1, 2026
Search Tags:#git#branching#workflow-automation#version-control#savepoint
One-click install
npx skills add https://github.com/pelchers/SessionSaver --skill savepoint-branching
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: savepoint-branching
Source: https://github.com/pelchers/SessionSaver/tree/main/.codex/skills/savepoint-branching
Command: npx skills add https://github.com/pelchers/SessionSaver --skill savepoint-branching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically create and push savepoint branches from the current commit state to capture work-in-progress milestones without disrupting the main line.

Core Features & Use Cases

  • Deterministic Savepoint Naming: Generate branch names in the format savepoint-<number>-<descriptor> and normalize user input to a safe, lowercase hyphen-case.
  • Post-Commit Branching: Create the savepoint from HEAD after a commit, push upstream, and switch back to the original branch.
  • Safe Recovery & Reporting: Report the created branch name and source commit hash, with guards against history rewrites.

Quick Start

Request a savepoint by instructing the AI to create a savepoint branch from the current commit state.

Frequently Asked Questions about savepoint-branching

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a git savepoint branch from my current commit state?▼

Git checkpoint branches are reproducible snapshots of your work-in-progress commit state, allowing you to capture milestones safely before switching contexts. They use deterministic branch naming to ensure each savepoint is traceable and recoverable later.

Does creating a savepoint branch rewrite git history?▼

No, the savepoint branching process includes explicit safeguards against history rewrites. It simply branches from your current commit state and pushes upstream, leaving the original commit history completely untouched.

What is the best way to automate git snapshots for work in progress?▼

The best way to automate git snapshots is to use a workflow that branches from HEAD post-commit, pushes the savepoint upstream with a normalized lowercase hyphen-case name, and switches back to your original branch automatically.

Can I normalize custom descriptors into git branch names safely?▼

Yes, you can normalize custom descriptors into git branch names safely. The workflow takes your input descriptor and normalizes it into a safe, lowercase hyphen-case format before generating the final deterministic savepoint branch name.

Do I need to manually switch back to my original branch after making a savepoint?▼

No, you do not need to manually switch back to your original branch. The post-commit branching workflow automatically switches you back to your original branch immediately after pushing the savepoint upstream.

Related Skills

Explore More Software Engineering Skills→
ether-moonether-moon

managing-git-workflow

Automate git commits, pushes, and pull request creation for local GitHub repositories.

Community
Advanced
dtsongdtsong
1

Git Merge Main

Merge the main branch into the current feature branch with conflict checks.

Community
Intermediate
markus41markus41
18

harness-code-integration

Automate Harness Code repository management, triggers, CI/CD pipelines, and GitOps for AWS EKS.

Community
Advanced
rintirinti

code-review

Evaluate uncommitted git diffs with Codex CLI review feedback.

Community
Advanced