checkin-validator

Name: checkin-validator
Availability: InStock
Author: shakhovskiya-create

Cross-reference sprint checkin claims against recent tool activity and emit warnings.

Updated May 5, 2026

Search Tags:#validation #evidence #honesty #sprint #log-analysis #checkin #tool-history

Ready to run

npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill checkin-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkin-validator
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/checkin-validator
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill checkin-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates honesty of /sprint:checkin claims by cross-checking against tool history. Detects fake claims, fake tests, and circular mocks, helping maintain trust in agile processes.

Core Features & Use Cases

Cross-checks checkin claims against recent tool activity to reveal inconsistencies.
Verifies supporting evidence, test execution claims, and time-tracking sanity.
Produces actionable honesty-warnings for SE review and logs them for auditing.

Quick Start

After every /sprint:checkin, run the validator and review the warnings in .sprints/active/honesty-warnings.log

Frequently Asked Questions about checkin-validator

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

FAQPage Schema

How do I validate sprint checkin claims against actual tool activity?▼

To validate sprint checkin claims, cross-reference the submitted claims against recent tool history. This detects fake tests and inconsistencies, producing actionable honesty-warnings for review and logging them for auditing.

What is the best way to detect fake evidence in agile sprint checkins?▼

The best way to detect fake evidence in sprint checkins is cross-referencing claims with recent tool activity. This identifies circular mocks and unsupported test execution claims, emitting warnings for software engineering review.

Can I use sprint checkin validation without blocking the development workflow?▼

Yes, you can validate checkin integrity without blocking the workflow. The validator applies non-blocking governance, emitting warnings and logging them for reviewer audit while allowing the sprint process to continue.

How do I review honesty warnings generated after a sprint checkin?▼

To review honesty warnings after a sprint checkin, open the .sprints/active/honesty-warnings.log file. This log captures all generated warnings regarding time-tracking sanity and unsupported claims for reviewer auditing.

Why does my sprint checkin validation produce timing inconsistencies?▼

Sprint checkin validation produces timing inconsistencies when claimed time-tracking does not align with recent tool activity logs. The validator performs time-tracking sanity checks to reveal these mismatches for further review.

Does checkin validation work with existing sprint workflows?▼

Yes, checkin validation works with existing sprint workflows by applying after the /sprint:checkin command. It assesses evidence, tests, and timing to ensure traceable governance over checkin integrity.