audit-drift

Audit application state across frontend, backend, and persistence layers to detect state management bugs.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/SebKay/skills --skill audit-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-drift
Source: https://github.com/SebKay/skills/tree/main/audit-drift
Command: npx skills add https://github.com/SebKay/skills --skill audit-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and helps resolve inconsistencies and errors in how application state is managed across different layers of a software system (frontend, backend, database).

Core Features & Use Cases

  • State Auditing: Analyzes state surfaces for impossible combinations, boolean explosion, magic strings, duplicated state, and source-of-truth violations.
  • Drift Detection: Pinpoints inconsistencies between different parts of the system where state should be synchronized.
  • Auto-fixing: Can automatically fix low-risk, local state issues.
  • Use Case: When a user reports a bug where a "paid" status is shown but the payment date is missing, this Skill can audit the state management logic to find the root cause of the inconsistency.

Quick Start

Use the audit-drift skill to find state inconsistencies in the user authentication flow.

Frequently Asked Questions about audit-drift

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

FAQPage Schema
How do I detect state management bugs across frontend and backend layers?

To detect state drift and data inconsistencies, you audit state surfaces across frontend, backend, and persistence layers. This inventory process finds impossible state combinations, duplicated state, and source-of-truth violations, yielding classified severity findings.

What causes impossible state combinations and boolean explosion in application state?

Impossible state combinations and boolean explosion in application state are caused by uncoordinated boolean flags and duplicated data across frontend, backend, and persistence layers. Auditing these state surfaces identifies the root source-of-truth violations and recommends structural fixes.

How do I fix inconsistent state like a paid status showing without a payment date?

To fix inconsistent state like a paid status showing without a payment date, you audit the state management logic to find the root cause of the drift. The audit classifies these data inconsistencies by severity and can auto-fix low-risk local state issues.

Can I automatically fix state management inconsistencies without manual code review?

You can automatically fix low-risk, local state management inconsistencies without extensive manual code review. The audit workflow identifies these local issues and provides options for auto-fixing, while classifying complex state drift findings for manual intervention.

What is the best way to inventory and classify state drift issues?

The best way to inventory and classify state drift issues is through a structured audit workflow that scans frontend, backend, and persistence layers. It classifies findings by severity from P1 to P4 and recommends targeted fixes for source-of-truth violations.