checkstate

Name: checkstate
Availability: InStock
Author: kangoxford

Reconstruct experiment narratives from git history and logs into status reports.

1|Updated Apr 23, 2026

Search Tags:#git #worktrees #logs #reporting #status #experiment #checkstate

Ready to run

npx skills add https://github.com/KangOxford/auto-quant-research --skill checkstate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkstate
Source: https://github.com/KangOxford/auto-quant-research/tree/main/execution-layer/skills/checkstate
Command: npx skills add https://github.com/KangOxford/auto-quant-research --skill checkstate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a structured, comprehensive status report for the current experiment or task by reconstructing the full narrative from git history, worktrees, checkpoints, job logs, and memory.

Core Features & Use Cases

Integrates multiple data sources to create a cohesive experiment storyline and output a standardized report that covers overall situation, progress, blockers, and planning.
Produces a three-section report detailing Overall Situation, Progress Details, and Summary & Planning, including timelines, completed steps, blockers, lessons, and next steps.
Supports onboarding, audits, long-running experiments, and handoffs by providing a reproducible narrative of state and decisions.

Quick Start

Ask the system to generate the current experiment status report using the latest git history, worktrees, checkpoints, and logs.

Frequently Asked Questions about checkstate

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

FAQPage Schema

How do I generate a status report from git history and worktrees?▼

To generate a status report from git history and worktrees, ingest your scattered artifacts like checkpoints and job logs to reconstruct the experiment's narrative into a structured, auditable report covering progress and next steps.

What is the best way to summarize an ongoing experiment for a handoff?▼

Summarizing an ongoing experiment for a handoff requires reconstructing the narrative from git history, worktrees, and memory to produce a standardized report detailing the overall situation, progress, blockers, and planning.

Can I use job logs and checkpoints to create a timeline of my experiment?▼

Yes, you can use job logs and checkpoints to create an experiment timeline by ingesting these artifacts alongside git history to produce a structured report covering completed steps, lessons, and next steps.

How does reconstructing experiment history from scattered artifacts work?▼

Reconstructing experiment history works by ingesting scattered artifacts like git history, worktrees, checkpoints, job logs, and memory to weave a cohesive storyline that outputs a three-section report on situation, progress, and planning.

Does generating a structured experiment report require manual timeline assembly?▼

Generating a structured experiment report does not require manual timeline assembly, as the process automatically ingests git history, worktrees, checkpoints, and job logs to build a reproducible narrative of state and decisions.

When do I need to reconstruct the narrative of my current experiment?▼

You need to reconstruct the narrative of your current experiment during active sessions, after breaks, or during handoffs to summarize the goal, history, timeline, progress, blockers, lessons, and next steps into a clear status report.