checkpoint

Organize documentation, commit verified changes, and push to a remote repository.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/olliecrow/codex --skill checkpoint-olliecrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/olliecrow/codex/tree/main/skills/checkpoint
Command: npx skills add https://github.com/olliecrow/codex --skill checkpoint-olliecrow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of saving your work by organizing documentation, committing changes to version control, and safely pushing them, ensuring consistent progress tracking for complex tasks.

Core Features & Use Cases

  • Knowledge Compounding: Organizes and promotes durable learnings and decisions into documentation.
  • Version Control: Creates small, logical commits for verified changes.
  • Safe Pushing: Pushes commits only when repository policy allows, preventing accidental pushes from local-only repositories.
  • Use Case: After completing a significant feature development phase, use this Skill to ensure all new knowledge is documented, the code is cleanly committed, and the changes are ready to be shared.

Quick Start

Run the checkpoint skill to organize documentation, commit verified changes, and push to the remote repository if applicable.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I automate git commit and push with documentation for long-running tasks?

To automate git commit and push with documentation, you can use a checkpoint cycle that organizes durable learnings, creates logical commits for verified changes, and safely pushes to a remote repository. This ensures consistent progress tracking for complex, multi-step workflows.

What is the best way to document decisions and commit changes in version control?

The best way to document decisions and commit changes is through an orchestrated checkpoint process that promotes durable learnings into documentation, verifies changes, and creates small, logical git commits to ensure durable knowledge capture and consistent version control.

How does safe pushing to a remote repository work for local-only git projects?

Safe pushing for local-only git projects works by checking repository push policies before executing the push. This prevents accidental pushes from local-only repositories by ensuring commits are only pushed when the remote repository policy explicitly allows it.

Can I save progress in a multi-step workflow without losing undocumented changes?

Yes, you can save progress in a multi-step workflow without losing undocumented changes by running a checkpoint cycle. This process organizes documentation, commits verified changes, and provides regular save points to ensure no knowledge is lost.

When should I create a checkpoint during feature development?

You should create a checkpoint during feature development after completing a significant phase. This ensures all new knowledge is documented, the code is cleanly committed to version control, and the changes are safely prepared for sharing.

Does this checkpoint workflow support local-only repositories without a remote?

Yes, the checkpoint workflow supports local-only repositories without a remote by adhering to repository push policies. It safely commits changes and organizes documentation while preventing accidental pushes when no remote is configured.