speckit-checkpoint-commit
Skill551 starsChanged 8 days agoApache-2.0View on GitHub
Commit changes at meaningful checkpoints throughout the workflow
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- backend/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- analyzing-ci-flakinessSkill
- audit-docsSkill
- commitSkill
- creating-changelog-entriesSkill
- creating-issuesSkill
- creating-prdSkill
- grilling-ideasSkill
- harvesting-reviewSkill
- migrate-feature-pageSkill
- monitoring-pull-requestsSkill
- neo4j-cypher-guideSkill
- opsmill-dev-analyzing-bugsSkill
- opsmill-dev-fixing-bugsSkill
- opsmill-dev-test-driving-bugsSkill
- pre-ciSkill
- prSkill
- rebaseSkill
- reviewing-pull-requestsSkill
- speckit-agent-context-updateSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-critique-runSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-opsmill-autoSkill
- speckit-opsmill-extractSkill
- speckit-opsmill-implementSkill
- speckit-opsmill-prepSkill
- speckit-opsmill-qaSkill
- speckit-opsmill-retrospectSkill
- speckit-opsmill-summarySkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- upgrading-infrastructure-dependenciesSkill
- what-is-this-prSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Commit immediately after each of these steps completes:
- Distinctive: line 25
After constitution — commit the project principles and guidelines
- Distinctive: line 26
After specify — commit the requirements and user stories
- Distinctive: line 27
After clarify — commit the resolved clarifications
- Distinctive: line 28
After plan — commit the technical implementation plan
- Distinctive: line 29
After analyze — commit the consistency and coverage analysis
- Distinctive: line 30
After tasks — commit the task breakdown
- Distinctive: line 34
Use the task list generated during the tasks step as a reference for when to commit.
- Very specific: line 46
Commit with the message (git commit -m "<message>")
- Distinctive: line 52
Keep messages concise but descriptive enough to understand the scope of the commit
- Distinctive: line 56
All current changes are staged and committed
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/speckit.checkpoint.commit
Description
Stages all current changes and creates a commit with a descriptive message reflecting the work just completed. This command should be called by the agent at two points during the spec-kit workflow:
- After each pre-implementation step (constitution, specify, clarify, plan, analyze, tasks) — to capture the spec artifacts produced by that step.
- During implementation — at natural checkpoints, such as after completing a task or a logical group of related tasks from the task list.
When to Commit
Pre-Implementation Steps
Commit immediately after each of these steps completes:
- After constitution — commit the project principles and guidelines
- After specify — commit the requirements and user stories
- After clarify — commit the resolved clarifications
- After plan — commit the technical implementation plan
- After analyze — commit the consistency and coverage analysis
- After tasks — commit the task breakdown
During Implementation
Use the task list generated during the tasks step as a reference for when to commit. Good checkpoints include:
- Completing a single task from the task list
- Completing a logical group of closely related tasks
- Finishing a self-contained unit of work (e.g., a new component, a service layer, a set of tests)
The agent should use judgment — the goal is to produce commits that are meaningful and reviewable, not to commit after every single file change.
Workflow
- Determine a clear, concise commit message based on the work just completed
- Stage all current changes (
git add -A) - Commit with the message (
git commit -m "<message>")
Commit Message Guidelines
- For pre-implementation steps, use the step name as a prefix (e.g.,
constitution: establish project principles,tasks: break down implementation into actionable items) - For implementation commits, describe what was built (e.g.,
implement user authentication service,add product listing page and API routes) - Keep messages concise but descriptive enough to understand the scope of the commit
Exit Criteria
- All current changes are staged and committed
- The commit message accurately reflects the work completed
- The working tree is clean after the commit
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

