lov-checkpoint

lov-checkpoint is a skill for Claude Code from lovstudio/skills. It costs 38 tokens per session (822 once invoked), scanned A, original, MIT.

A project checkpoint tool that records what changed, what was verified, unresolved work, and the next steps using Git status and history. Git is the system that tracks changes to project files.

In plain words
What is it for?
Use it to update a checkpoint log, reconcile related README or configuration notes, and optionally commit only the verified files when asked.
Why use it?
It prevents milestone notes from being based on assumptions or stale timestamps and keeps the record tied to actual changes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the dev-tools plugin — 77 skills shipped together

Good fit Use it to update a checkpoint log, reconcile related README or configuration notes, and optionally commit only the verified files when asked.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lovstudio/skills/checkpoint
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add lovstudio/skills --skill checkpoint
Clone the repo
git clone --depth 1 https://github.com/lovstudio/skills

Made for: Claude Code.

Or install dev-tools, the plugin that ships this one along with the rest of its 77 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for lov-checkpoint

README.md
[![agentmods](https://agentmods.dev/badge/skills/lovstudio/skills/checkpoint.svg)](https://agentmods.dev/skills/lovstudio/skills/checkpoint)
Your own site
<a href="https://agentmods.dev/skills/lovstudio/skills/checkpoint"><img src="https://agentmods.dev/badge/skills/lovstudio/skills/checkpoint.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 822 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00822
Opus 5 $0.00019 $0.00411
Sonnet 5 $0.00008 $0.00164
Haiku 4.5 $0.00004 $0.00082

Measured today against content hash e9fbe130c017, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

lov-checkpoint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/profile_store.py, scripts/validate_skill.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/checkpoint/SKILL.md · 66 lines

What it actually says

项目存档 · Project Checkpoint

根据当前 Git 差异和历史记录保存项目里程碑及后续事项。

Triggers

Activate when

  • “根据当前 Git 差异和历史记录保存项目里程碑及后续事项。”
  • “Create a project checkpoint.”

Do not activate when

  • 只是查询本 Skill 的说明,或请求与上述结果无关的任务;不执行实际业务操作。
  • 用户仅要预览或审查时,不进入修改、提交或发布分支。

Execution boundary

自然语言请求即可触发;无需旧 slash 路径、参数插值或指定助手。明确解析当前请求中的 项目、目标文件、选项与输出位置;用当前宿主实际提供的文件、搜索、CLI 和浏览器能力。 项目依赖版本与外部 API 在执行时核实,不能假设示例是现行配置。随包脚本从 Skill 根解析, 业务文件从目标项目根解析。先读当前状态,保护已有未提交内容与其他任务的暂存区。 分析、预览请求保持只读;修改、提交、推送、部署和发布各依当前请求的明确范围执行。 不绕过保护、自动发送消息、强制结束用户进程或抢前台。失败保留可诊断原始错误。

Workflow

  1. 读取 Git 状态、暂存区、最近历史、.checkpoint_log 与项目指定记录文件。旧 Claude Code 记录可作为兼容输入,写新记录时不伪造任何宿主署名。

  2. 确定上次检查点到当前的真实变化,首次运行采用存在的提交范围。记录里程碑、验证证据、未解决事项和下一步,不凭修改时间断言文档过期。

  3. 在请求范围内修正与实现矛盾的 README 或配置说明,不重写仍有效内容;版本和 CHANGELOG 保持事实一致。

  4. 向 .checkpoint_log 安全追加 JSONL,记录时间、项目、分支、上个哈希、变化与验证结果;项目记录默认放检查点文档,不把每次日志塞进全局 Agent 指令。

  5. 用户要求检查点提交时仅暂存已核验的本次文件,检查最终暂存集合并执行正常 hooks;未授权提交时交付记录。报告日志与提交各自真实状态,重复运行避免空重复记录。

Composition

执行前读取 能力组合,按明确制品交接相邻能力。

Runtime context (shared)

运行前读取本包 skill.yamlProfile 合同。优先级为当前请求、 项目上下文、本 Skill records、共享 preferences、brand/user Profile、安全默认值。 只读取声明字段;没有专用运行时的宿主可使用 scripts/profile_store.py 读取共享 Profile。 配置缺失只问影响结果的一个问题。用户明确要求长期保存的值通过该脚本原子写入, 报告实际路径;不保存推断、凭据或其他任务的资料。

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 66 lines · 38 tokens per session scan A e9fbe130c017

Subscribe to this mod's changes

lov-checkpoint is a skill published in the GitHub repository lovstudio/skills (64 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 822 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.

Related

Other skills, from other repositories

branch-surgery-pr-split

Split oversized or mixed-concern branches into smaller, reviewable PR stacks with safety refs, topology selection, parity audits, and merge sequencing. Use when a PR or branch is too large, difficult to review, mixed across concerns, conflict-prone, or needs to be decomposed without losing net changes.

liatrio-labs/ai-prompts · 68 tokens

update-pr-summary

This skill should be used when user asks to "update PR summary", "update PR description", "rewrite PR body", "refresh PR title and body", or explicitly invokes "update-pr-summary".

fcakyon/claude-codex-settings · 43 tokens

clean-gone-branches

This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".

fcakyon/claude-codex-settings · 44 tokens

ijfw-ship

Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…

FerroxLabs/ijfw · 139 tokens

revert

Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.

drafthq/draft · 66 tokens

workspace-branch

Use when setting up workspace and branch context, switching workspaces or branches, creating or deleting branches, reviewing branch history, or creating a pull request for a working branch. This skill should be used when the user asks to "list workspaces", "switch workspace", "create a branch", "delete a branch"…

honeydew-ai/honeydew-ai-coding-agents-plugins · 92 tokens