ada-stateful-service-audit

Audits mutation paths, transactions, concurrency, and undo/redo invariants in stateful services.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-stateful-service-audit-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-stateful-service-audit
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-stateful-service-audit
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-stateful-service-audit-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stateful services often claim that all changes flow through validated commands, yet interop callbacks, restore paths, or direct model writes silently bypass invariants, transactions, and notifications. This Skill reconstructs the real mutation topology and verifies that every entry point preserves the same contracts. ## Core Features & Use Cases - Mutation-Boundary Matrix: Traces every production call path (UI, API, interop, restore, direct mutation) and records whether each route is validated, serialized, atomic, undoable, evented, and persisted. - Invariant and Transaction Verification: Checks execute/no-op/failure/undo/redo behavior, export-import round-trip fidelity, failure atomicity, and history invalidation after restore. - Concurrency and Adversarial Probes: Audits linearization points, revision models, stale async guards, cancellation, disposal drains, event reentrancy, and undo/redo coalescing. - Use Case: A Blazor application claims all edits go through commands, but JavaScript resize callbacks write state directly. The audit maps every caller, finds the bypass, names the violated invariant, and lists the missing regression tests. ## Quick Start Ask the agent to audit all mutation paths, import atomicity, events, auto-save, and undo/redo behavior of a specific store or service in your repository.

Frequently Asked Questions about ada-stateful-service-audit

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

FAQPage Schema
How do I audit all mutation paths in a stateful service?

Trace each operation family from UI, API, or interop entry points through validation, state commit, events, history, and persistence. Build a mutation-boundary matrix recording whether every state-writing route is validated, serialized, atomic, undoable, evented, and persisted.

How to verify undo/redo correctness after state restore?

Check that restore invalidates or barriers stale history entries, even when the restored state is semantically equal. Verify operation algebra is closed for undo/redo, failure ordering is explicit, and coalescing keys separate independent gestures.

When should I use a stateful service audit instead of debugging?

Use the audit when a service owns aggregate invariants across commands, persistence, events, and concurrency. If only one isolated bug is already located, use systematic debugging first rather than broadening into a full audit.

Does this audit apply to stateless functions or CRUD wrappers?

No. Stateless transformations and CRUD wrappers without aggregate invariants are out of scope. Broad security or complexity grading across a whole repository should go to a code-quality analysis pipeline instead.

What concurrency issues does a stateful service audit check?

It identifies the linearization point, revision model, lock scope, cancellation semantics, and disposal drain behavior. It also probes stale async guards, last-waiter cancellation while callbacks continue, and synchronous event reentrancy inside non-reentrant locks.

Why do import and restore paths break failure atomicity?

Apply operations that commit incrementally can leave partial state when validation fails mid-flight. The audit requires validation before commit, unchanged state on failure, and prefers shadow-state validation with swap or explicit snapshot/rollback.