checkpoint

Summarize progress, stage changes, and commit with conventional messages.

2|Updated Feb 13, 2026

Search Tags:#git #workflow #commit #checkpoint #progress #standup #task-tracking

Ready to run

npx skills add https://github.com/sakebomb/scaffold --skill checkpoint-sakebomb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/sakebomb/scaffold/tree/main/.claude/skills/checkpoint
Command: npx skills add https://github.com/sakebomb/scaffold --skill checkpoint-sakebomb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to capture a concise snapshot of ongoing work by summarizing progress, staging relevant changes, and recording decisions in the task log, ensuring a traceable checkpoint before moving forward.

Core Features & Use Cases

Progress summarization: generate a short summary of changes and remaining work.
Automatic commit discipline: stage and commit changes with a clear message following conventional commits.
Task-tracking integration: update the tasks/todo.md with completed items and blockers.

Quick Start

Run the checkpoint to summarize progress, stage changes, and update the task log.

Frequently Asked Questions about checkpoint

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

FAQPage Schema

How do I summarize my git progress and create a commit checkpoint?▼

To create a commit checkpoint, you summarize your git progress by analyzing git status and git diff, staging relevant changes and committing them with a conventional commit message. This records a traceable snapshot of your ongoing work before moving forward.

What is the best way to document my working state for a standup?▼

Documenting your working state for a standup involves summarizing current changes and updating your task tracking log with completed items and blockers. This captures a concise snapshot of ongoing work to document progress and lock in changes.

Can I automatically update my task tracking when I commit changes?▼

Yes, you can update task tracking when you commit changes by integrating the commit process with your tasks/todo.md file. This automatically records completed items and blockers while staging and committing your working state.

Does this checkpoint workflow follow conventional commit messaging?▼

Yes, the checkpoint workflow follows conventional commit messaging to maintain automatic commit discipline. It stages your changes and commits them with a clear, conventional message to ensure a traceable checkpoint.

How do I avoid staging sensitive files when committing my git progress?▼

To avoid staging sensitive files when committing your git progress, the checkpoint process explicitly avoids staging them while selecting only relevant changes from your working state. This ensures a secure commit without exposing sensitive data.

When do I need to create a git commit checkpoint during a sprint?▼

You need to create a git commit checkpoint during a sprint review or standup to document progress and lock in changes. It is useful in git-driven projects to capture a concise snapshot of ongoing work and record decisions in the task log.