install-implicit-statescript
/install-implicit-statescript
Vendor the implicit-statescript Oxlint plugin into a TypeScript repository, register its rules at warn, and run the type-aware scattered-literals scan. Use when asked to add implicit state machine checks, find flags or marker files that spell a hidden state, or install implicit-statescript.
- Author
- s-smits ↗
- Repository
- implicit-statescript ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Vendor the implicit-statescript Oxlint plugin into a TypeScript repository, register its rules at warn, and run the type-aware scattered-literals scan. Use when asked to add implicit state machine checks, find flags or marker files that spell a hidden state, or install implicit-statescript.
Original author description
Vendor the implicit-statescript Oxlint plugin into a TypeScript repository, register its rules at warn, and run the type-aware scattered-literals scan. Use when asked to add implicit state machine checks, find flags or marker files that spell a hidden state, or install implicit-statescript.
How it works
SKILL.md has no level-two headings · 34 lines, 304 words
SKILL.md preview
---
name: install-implicit-statescript
description: Vendor the implicit-statescript Oxlint plugin into a TypeScript repository, register its rules at warn, and run the type-aware scattered-literals scan. Use when asked to add implicit state machine checks, find flags or marker files that spell a hidden state, or install implicit-statescript.
---
# Install implicit-statescript
1. Copy `src/` from this repository into the target repository as
`vendor/implicit-statescript/src/`, leaving out every `*.test.ts` file and keeping
`src/package.json`, which marks the folder as an ES module.
2. Install the runtime dependencies with the target's package manager, pinned as here:
`oxlint@1.83.0` and `@oxlint/plugins@1.83.0`, and `typescript5@npm:typescript@5.9.3` if the
scan is wanted.
3. Register the plugin in the target's Oxlint config. In `.oxlintrc.json`, add
`./vendor/implicit-statescript/src/configs/recommended.json` to `extends`, which loads the plugin
and sets `implicit-state/no-age-based-lock`, `implicit-state/no-coupled-flags` and
`implicit-state/no-marker-file-state` to `"warn"`; extend `opinionated.json` instead only if the
owner also wants `implicit-state/prefer-state-union`. In `oxlint.config.ts`, add
`{ "name": "implicit-state", "specifier": "./vendor/implicit-statescript/src/index.ts" }` to
`jsPlugins` and set the same rules to `"warn"`. Merge with the existing config; do not replace
it.
4. Run Oxlint (`bunx oxlint <src folder>`, or `bun x --bun oxlint <src folder>` where Node is
older than 22.18 or absent) and read every implicit-state warning before proposing a change.
The measured precision rests on small labelled counts, and `prefer-state-union` was right on
about half of its labelled hits, so report hits as places to look, not defects. Raise a rule to
`error` only on the owner's word.
5. Optionally run the scan, which needs Bun:
`bun vendor/implicit-statescript/src/scan/cli.ts scan <src folder>`. Add `--error` to gate on it
in CI, and `--config <the Oxlint config>` once it holds `settings["implicit-state"]`.
6. Where the rules report settings records as states, or miss a helper the repository wraps the
file system in, offer to tailor them: `tailor-implicit-statescript` runs
`bun vendor/implicit-statescript/src/scan/cli.ts survey <src folder>` and adopts its proposals
as options one at a time, on the owner's word.
Each rule has no automatic fix. Where the owner asks for one, name the states in one union or
field, give it one owner that moves between them, and replace the flags, marker files or hand
groupings with reads of that owner.
Versions
The database has no other skills named install-implicit-statescript.
Database snapshot: 13.11.2026 · package version fe9ac00edcb5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86tailor-implicit-statescript
Fit the implicit-statescript rules and scan to one repository by asking its owner to adopt the facts the survey proposes (settings records, state types, owners, wrappers, state folders), writing each adopted fact as a rule option, and keeping a rule only where the owner's labels… - 100find-implicit-state-machines
Find implicit state machines in a codebase (state spread across flags, status fields, timers and callbacks), audit for defects, or catalog identified machines when explicitly asked for an inventory. Use when asked to find implicit state machines or audit for impossible states,… - 90no-more-implicit-fsms
Audit a codebase for implicit state machines — lifecycle and mode logic spread across boolean flags, nullable fields, status strings, file locations and retry counters instead of one explicit state type — and grade the failure modes they create: wedges with no exit, lost… - 100migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint. - 96dot-agent-oxlint
Run the advisory Oxlint pass on JavaScript or TypeScript changes in dot-managed repositories. Use after the repository's own lint workflow whenever a task changes JS or TS files; the command checks private opt-in and local Oxlint precedence and reports only findings on changed lines. - 100oxlint-typescript-conventions
WHAT: Write TypeScript under `lib/node/`, `tests/`, and `config/pi/` that passes the repo's strict `oxlint --type-aware` configuration on the first try, so the husky pre-commit hook does not reject the commit. WHEN: User asks to add or edit a `.ts` / `.spec.ts` file anywhere…