Find Implicit State Machines
Audit a codebase for implicit state machines (state spread across flags, status fields, timers and callbacks). Use when asked to find them or to trace impossible states, stuck loading, missing resets or async races. Catalog machines with no defect only when asked for an inventory.
Install
npx skills add kr4chinin/skills --skill find-implicit-state-machinesgit clone --depth 1 https://github.com/kr4chinin/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/find-implicit-state-machines ~/.claude/skills/find-implicit-state-machinesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Find implicit state machines An implicit state machine has states and transitions that are not declared in one place but spread across variables, handlers, callbacks and timers. Finding a machine does not mean finding a bug. Stay read-only: don't edit code or create tickets unless asked. ## 1. Scope Use the scope the user gave. If the repository holds several apps and there is no hint, ask which one. Default to a defect audit: report the broken or fragile machines. A request to find all the machines is still that audit. Only an explicit request for an inventory (for example, "catalog all machines, including ones with no defect") adds a compact catalog with locations and review outcomes, including "no defect found" for fully traced machines without a finding. Suspected defects are still investigated and labelled as below. In either mode, report what you included and skipped: distinguish discovery scope (where you searched), fully traced paths, and unreviewed candidates. State coverage gaps; search hits and file counts do not establish exhaustive coverage. ## 2. Find candidates Prioritize units (module, component, class, service) where two or more of these signals meet; a concrete reachable failure can warrant tracing a candidate with only one signal: - several booleans describing one process; - a status, phase or step field assigned from many places, with no transition table; - mutable references or instance fields used as state;
Details
- Skill name
find-implicit-state-machines- Repository
- kr4chinin/skills
- Path
skills/find-implicit-state-machines/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Find Implicit State Machines skill do?
Audit a codebase for implicit state machines (state spread across flags, status fields, timers and callbacks). Use when asked to find them or to trace impossible states, stuck loading, missing resets or async races. Catalog machines with no defect only when asked for an inventory.
How do I install the Find Implicit State Machines skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add kr4chinin/skills --skill find-implicit-state-machines. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Find Implicit State Machines popular?
It lives in kr4chinin/skills, which has 9 GitHub stars and 0 forks.
Related skills
Convert State Machines to Actors
9kr4chinin/skills
Convert a database-backed implicit state machine to an actor, the one owner every writer of the persisted state goes through. Use when asked to put writers behind one owner, or to fix a race or lost update across several writers, such as a find-implicit-state-machines finding.
Prune Comments
9kr4chinin/skills
Audit code comments and plan which to delete, keep, rewrite or replace with a refactor. Use when asked to prune a codebase's comments, or to sort workaround comments into root-cause fixes and safe deletions.
Recover Semantic Model
9kr4chinin/skills
Recover a program's minimal semantic model (the state that changes what users see, how its transitions repeat and reorder, what each effect requires). Use when asked to recover or audit that model, to check what is idempotent or order-dependent, or to split a refactor into provably equivalent and "trust me" changes.
Migrate Placements
9adaptyteam/adapty-skills
Use when someone wants to move an app from paywall placements to Flow Builder flows — "migrate my placements to flows", "switch my paywalls to flows", "we have 40 placements on paywalls and want flows", or a bulk request across many apps or paywalls. Creates NEW flow placements alongside the existing paywall ones and hands back the old→new mapping plus the SDK call change. Never converts a placement in place — the backend refuses a type change. Complements `flow-generator` (which builds and publishes flows) and `adapty-integration` (which owns the app-side call sites).
Audiences
9adaptyteam/adapty-skills
Use when a user wants different users to see different paywalls or flows at the same placement — by country, language, app version, platform, revenue, subscription state, install date, a custom attribute, or attribution — or wants to create, edit or reuse an Adapty segment through the CLI. Triggers on "show this paywall only to users in Germany", "target users on version 2.0", "a cheaper paywall for non-payers", "users with my custom attribute should see…", "create a segment", "add an audience to my placement", "who sees which paywall".
Mxl CLI
9TaoELi/MaxwellLink
This skill should be used when users need to initialize, clean, or configure MaxwellLink workspaces using the mxl command family.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.