checkpoint

Reviews accumulated ticket implementations across commit intervals for cross-session consistency defects.

2|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/GeraldoNeto123/ticket --skill checkpoint-geraldoneto123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/GeraldoNeto123/ticket/tree/main/skills/checkpoint
Command: npx skills add https://github.com/GeraldoNeto123/ticket --skill checkpoint-geraldoneto123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Tickets are implemented one per session, and each session only sees its own ticket, so defects spanning multiple tickets go unnoticed. This Skill runs a transversal consistency review over the accumulated work of several tickets, catching what no isolated session could see. ## Core Features & Use Cases - Interval-based review: Delimits each review cycle by the checkpoint commits already in git history (refactor: checkpoint / docs(checkpoint):), so markers travel with the clone without tags or hooks. - Reviewer agent dispatch: Launches the checkpoint-reviewer agent with the commit interval, ticket locations, and the batch of closed tickets, returning a four-list report without modifying code. - Quarantine routing: Routes real defects into a quarantine container (files under .scratch/<feature>/checkpoint/ or labeled tracker comments) with an explicit human promotion criterion, keeping the feature queue from growing. - Use Case: After every five tickets closed in an autonomous /ticket:run queue, invoke this Skill to review the accumulated commits, apply small fixes in a single checkpoint commit, and file cross-ticket findings for human triage. ## Quick Start Ask the AI to run a checkpoint review over the tickets closed since the last checkpoint commit and route any findings into quarantine.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I review consistency across multiple implemented tickets?▼

Run a checkpoint review over the commit interval since the last checkpoint. It dispatches a reviewer agent with the interval and the batch of closed tickets, returning a four-list report of defects, inconsistencies, and process proposals.

How does the checkpoint determine which commits to review?▼

It searches git history for the last commit with subject `refactor: checkpoint` or `docs(checkpoint):` and reviews from there to HEAD. In a queue run, the ledger's checkpoint line names the same SHA and takes precedence on divergence.

Can checkpoint findings be stored in GitHub or GitLab issues?▼

Yes, findings live either as files under `.scratch/<feature>/checkpoint/` or as labeled comments on the parent issue. GitHub defaults to tracker because `gh search issues --match comments` reaches comments; GitLab defaults to file because its search stops at title and description.

When does a quarantined finding become a real ticket?▼

Only when it produces wrong data for the client through a reachable path, or when the same anchor recurs in two different checkpoints. Everything else is closed as wontfix during human triage, keeping the queue from growing.

What happens if a checkpoint finds nothing to fix?▼

It still creates a cycle marker: a `docs(checkpoint):` commit recording the interval with no findings. Without that marker, the next checkpoint would review the same tickets again.