Skip to content

KamiJeong/tech-bridge-book / .agents/skills/speckit-checkpoint-commit

speckit-checkpoint-commit

Verified

Commit changes at meaningful checkpoints throughout the workflow

/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:

  1. After each pre-implementation step (constitution, specify, clarify, plan, analyze, tasks) — to capture the spec artifacts produced by that step.
  2. 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

  1. Determine a clear, concise commit message based on the work just completed
  2. Stage all current changes (git add -A)
  3. 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
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 117kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall