checkpoint — community checkpoint, TML-bench, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Git-integrated AI Agents requiring automated preflight checks and sanity guardrails for version control consistency. Create a safe checkpoint git commit on the current branch (avoid competition data, runs, artifacts, secrets).

MykolaPinchuk MykolaPinchuk
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
23
Canonical Locale
en
Detected Body Locale
en

Ideal for Git-integrated AI Agents requiring automated preflight checks and sanity guardrails for version control consistency. Create a safe checkpoint git commit on the current branch (avoid competition data, runs, artifacts, secrets).

Core Value

Empowers agents to automate Git consistency checks using `git status` and `git diff --stat`, while ensuring `agent_logs/current.md` synchronization and preventing accidental pushes or commits of secrets via `.env*`, `*.pem`, or `*.key` files.

Ideal Agent Persona

Ideal for Git-integrated AI Agents requiring automated preflight checks and sanity guardrails for version control consistency.

↓ Capabilities Granted for checkpoint

Automating preflight checks for Git commits
Verifying `agent_logs/current.md` synchronization
Preventing accidental pushes of sensitive data

! Prerequisites & Limits

  • Requires Git installation and configuration
  • Limited to preventing specific Git commands like `git push`, `git commit --amend`, and `git rebase`

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is checkpoint?

Ideal for Git-integrated AI Agents requiring automated preflight checks and sanity guardrails for version control consistency. Create a safe checkpoint git commit on the current branch (avoid competition data, runs, artifacts, secrets).

How do I install checkpoint?

Run the command: npx killer-skills add MykolaPinchuk/TML-bench/checkpoint. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for checkpoint?

Key use cases include: Automating preflight checks for Git commits, Verifying `agent_logs/current.md` synchronization, Preventing accidental pushes of sensitive data.

Which IDEs are compatible with checkpoint?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for checkpoint?

Requires Git installation and configuration. Limited to preventing specific Git commands like `git push`, `git commit --amend`, and `git rebase`.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add MykolaPinchuk/TML-bench/checkpoint. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use checkpoint immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

checkpoint

Install checkpoint, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

When invoked (or when the user says checkpoint), do this in order.

1) Preflight (must do; show output)

  • git status
  • git diff --stat
  • Verify agent_logs/current.md id: is synced to the kickoff AgentNN for this chat. If stale, fix current.md before commit.

2) Sanity guardrails (must do)

  • Never run: git push, git commit --amend, git rebase, git reset --hard, git clean -fdx, or modify git remotes.
  • Never stage/commit secrets/credentials: .env*, *.pem, *.key, id_rsa*, id_ed25519*, tokens.
  • Never stage/commit competition data or run artifacts:
    • competitions/**/{public,private,raw,downloads}/**
    • runs/**
    • sqlite/db files

3) Stage (default: include safe tracked files)

Stage only source/docs/config files and small markdown:

  • root *.md, *.yml
  • docs/**
  • local_context_enrichments/**
  • .codex/**

If anything looks suspicious (bulk files, data-like payloads), stop and report before staging.

Before committing, show:

  • git diff --cached --stat

4) Commit (auto message)

  • Create a structured message that includes the agent id:
    • agentNN: checkpoint(<area>): <short summary>
    • Derive agentNN from kickoff-synced agent_logs/current.md (field id:). If missing/ambiguous, stop and ask the human.
    • Choose <area> from: workflow, docs, orchestrator, competitions, prompts, ci, misc.
  • Run git commit -m "<message>".

5) Postflight (must do; show output)

  • git status
  • Report the commit hash.

Related Skills

Looking for an alternative to checkpoint or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer