checkpoint

Stage all changes and create a descriptive checkpoint commit after lint, type-check, and build pass.

Updated May 14, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/vector --skill checkpoint-leroyadonis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/LeroyAdonis/vector/tree/main/.agents/skills/checkpoint
Command: npx skills add https://github.com/LeroyAdonis/vector --skill checkpoint-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a comprehensive checkpoint commit that captures all changes — but only after the code passes lint, type-check, and build. It stages all changes and creates a descriptive commit, and it does not push.

Core Features & Use Cases

  • Stages all changes (tracked, untracked, and deletions) and creates a descriptive checkpoint commit.
  • Requires lint, type-check, and build to pass before committing to ensure a clean checkpoint.
  • Use Case: before shipping a feature, snapshot progress with a detailed checkpoint message.

Quick Start

Run the checkpoint workflow to stage all changes and create a descriptive checkpoint commit after all checks pass.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I create a git checkpoint commit only after lint and build pass?

To create a git checkpoint commit, this workflow automatically stages all tracked, untracked, and deleted changes, then commits them with a descriptive message only after lint, type-check, and build pass.

What is the safest way to snapshot development progress before shipping a feature?

A safe progress snapshot requires passing lint, type-check, and build validations first. This ensures a clean, auditable checkpoint commit capturing all current changes without automatically pushing to a remote repository.

Do I need to manually stage untracked files for a checkpoint commit?

No, you do not need to manually stage untracked files. The checkpoint process automatically stages all changes—including untracked files and deletions—before generating a conventional commit message.

Does this checkpoint workflow push commits to the remote repository automatically?

No, the checkpoint workflow does not push commits automatically. It strictly stages changes and records the commit locally after build and lint checks pass, giving you full control over remote synchronization.

Why should I use an automated checkpoint commit instead of a standard git commit?

An automated checkpoint commit enforces quality by requiring lint, type-check, and build to pass before committing. This prevents broken progress snapshots and generates descriptive commit messages for better auditability.