skills.rest
Vimurai
VimuraiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ai-sync-verify

Verify TASKS.md and REVIEWS.md agree with state.sqlite via the task-synchronizer MCP tool.

Updated Feb 26, 2026
Search Tags:#markdown#verification#mcp#sqlite#task synchronization#ai-os#state consistency
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill ai-sync-verify-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-sync-verify
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/ai-sync-verify
Command: npx skills add https://github.com/Vimurai/ai-os --skill ai-sync-verify-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-OS projects track tasks in both Markdown files (TASKS.md, REVIEWS.md) and a SQLite state database, and these two sources can silently drift apart — for example, a task is checked off in TASKS.md but still OPEN in state.sqlite. This Skill detects those mismatches before you trust the task list or claim work is done. ## Core Features & Use Cases - One-step sync verification: Wraps the task-synchronizer-mcp verify_markdown_sync tool and returns a SYNC_PASS or SYNC_FAIL verdict. - Structured anomaly interpretation: Parses the SYNC_RESULT JSON tail (status, anomalies, auto_fixes) and maps each failure pattern to a concrete fix. - Done-claim gate: Blocks "work is done" claims until a SYNC_FAIL is resolved, routing status fixes through the ai-task skill. - Use Case: Before committing, run the check and discover that E-178 is marked [x] in TASKS.md but still OPEN in state.sqlite, then fix it via the ai-task skill instead of shipping inconsistent bookkeeping. ## Quick Start Ask the AI to verify that TASKS.md and the project state database are in sync before marking any task as done.

Frequently Asked Questions about ai-sync-verify

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

FAQPage Schema
How do I check if TASKS.md matches the SQLite state database?▼

Invoke the verify_markdown_sync tool from task-synchronizer-mcp, which compares TASKS.md and REVIEWS.md against state.sqlite. It returns a SYNC_PASS or SYNC_FAIL result with a JSON tail listing anomalies and auto-fixes.

What does a SYNC_FAIL result mean in task synchronization?▼

SYNC_FAIL means the markdown files and state.sqlite disagree, such as a task checked [x] in TASKS.md but still OPEN in the database. The JSON tail lists each anomaly so you can resolve it before claiming work is done.

Does verify_markdown_sync automatically fix mismatches?▼

It auto-regenerates TASKS.md or REVIEWS.md when rows are missing from one side, but it intentionally does not fix checkbox-versus-status mismatches. Those require an explicit decision and must be resolved through the ai-task skill.

Can this skill mark a task as DONE to fix a sync anomaly?▼

No, the skill is read-only over task state and never marks tasks DONE. To resolve a [x]-but-OPEN anomaly, route through the ai-task skill rather than calling update_task_status directly.

When should I run the markdown sync verification?▼

Run it during preflight before trusting the open-task list, before claiming work is done, after another agent edited .ai/ files, and before commits as part of the review gate. A SYNC_FAIL blocks done claims until resolved.

Related Skills

Explore More Software Engineering Skills→
dianedefdianedef

shipflow-init

Detect technology stacks and generate CLAUDE.md and TASKS.md files for new projects.

Community
Advanced
tdp1999tdp1999

sync

Align progress.md with task files and archive completed tasks.

Community
Advanced
gqf2008gqf2008

requesting-code-review

Automate pre-commit verification with static security scans and quality gates.

Community
Intermediate
kestevakesteva
42

visual-verify

Automate UI verification across mobile, web, and macOS platforms.

Community
Advanced