Summarize progress, stage changes, and commit with conventional messages.
npx skills add https://github.com/sakebomb/scaffold --skill checkpoint-sakebomb
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
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.
Run the checkpoint to summarize progress, stage changes, and update the task log.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Marshall-HallenbeckGroup working-tree changes into conventional git commits with issue references.
ThrookieGenerate daily and weekly progress reports from git history.
tikazyqMonitor execution plan progress and track SubPlan and Round statuses.
mjohnson518Automate multi-project sprint planning and daily task coordination across repositories.
