skills.rest
cosmicdreams
cosmicdreamsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reset-state

Resets Drover log processing offsets to stop duplicate ticket creation after corruption or deletion.

Updated Feb 28, 2026
Search Tags:#beads#deduplication#ddev#ticket triage#state recovery#drover#log offsets
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill reset-state
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reset-state
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/drover/skills/reset-state
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill reset-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents duplicate “ticket storm” behavior when Drover’s state file is corrupted or missing by resetting log-processing offsets safely.

Core Features & Use Cases

  • Soft reset to the log tail: Updates offsets to the current end of the logs so Drover only processes new entries going forward.
  • Hard reset with dedup guard: Resets offsets to zero and loads known error fingerprints from the Beads board to avoid recreating duplicates while rescanning.
  • Targeted resets by environment: Supports resetting a single environment by name or resetting all environments in the project config, reducing operational blast radius.

Quick Start

Ask your AI to run drover:reset-state with the environment you need to recover, using soft reset first, and switch to hard reset only if duplicates persist.

Frequently Asked Questions about reset-state

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

FAQPage Schema
How do I stop duplicate ticket creation when Drover state is corrupted?▼

To stop duplicate ticket storms from corrupted Drover state, reset log-processing offsets using a soft reset to the current log tail. This updates the state file so only new log entries trigger ticket creation moving forward.

What is the difference between a soft reset and a hard reset for Drover log offsets?▼

A soft reset sets Drover log offsets to the current tail to process only new entries. A hard reset sets offsets to zero and applies a Beads-driven dedup guard to prevent recreating duplicates while rescanning old logs.

Can I reset Drover state for a single environment instead of all environments?▼

Yes, you can reset Drover state for a single environment by name or reset all environments in the project config. Targeted resets reduce operational blast radius during recovery from tail-offset drift or outages.

How does the Beads deduplication guard work during a hard state reset?▼

The Beads deduplication guard loads known error fingerprints from the Beads board during a hard reset. It prevents Drover from recreating duplicate tickets by checking rescanned log entries against these existing fingerprints.

When should I use a hard reset over a soft reset for Drover state recovery?▼

Use a hard reset over a soft reset when duplicate tickets persist after applying a soft reset. The hard reset rescans from zero offsets while relying on the Beads dedup guard to suppress known duplicate error fingerprints.

Related Skills

Explore More Software Engineering Skills→
cosmicdreamscosmicdreams

run

Launch drover error monitoring with pre-flight checks and parallel triage.

Community
Advanced
cosmicdreamscosmicdreams

verify

Promote a drover ticket's Projected fields into an Actual verified record.

Community
Intermediate
bdambrosiobdambrosio
10

osworld-reset

Reset the OSWorld environment via soft or hard modes.

Community
Basic
cosmicdreamscosmicdreams

solution

Document verified drover ticket solutions with root cause, fix summary, and commit SHA.

Community
Intermediate