agentleFS
opsmillopsmill/infrahub/.agents/skills/speckit-checkpoint-commit/SKILL.md

speckit-checkpoint-commit

Skill551 starsChanged 8 days agoApache-2.0View on GitHub

Commit changes at meaningful checkpoints throughout the workflow

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
  1. Distinctive:

    Commit immediately after each of these steps completes:

    line 23
  2. Distinctive:

    After constitution — commit the project principles and guidelines

    line 25
  3. Distinctive:

    After specify — commit the requirements and user stories

    line 26
  4. Distinctive:

    After clarify — commit the resolved clarifications

    line 27
  5. Distinctive:

    After plan — commit the technical implementation plan

    line 28
  6. Distinctive:

    After analyze — commit the consistency and coverage analysis

    line 29
  7. Distinctive:

    After tasks — commit the task breakdown

    line 30
  8. Distinctive:

    Use the task list generated during the tasks step as a reference for when to commit.

    line 34
  9. Very specific:

    Commit with the message (git commit -m "<message>")

    line 46
  10. Distinctive:

    Keep messages concise but descriptive enough to understand the scope of the commit

    line 52
  11. Distinctive:

    All current changes are staged and committed

    line 56

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.