migrate-to-rslint
Migrate ESLint flat config or Oxlint to Rslint, preserving rule options, file scopes, and plugins while updating lint scripts, editor settings, and inline directives.
How do I install this agent skill?
npx skills add https://github.com/rstackjs/agent-skills --skill migrate-to-rslintIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is a migration tool designed to automate the transition from ESLint or Oxlint to Rslint. It performs expected operations such as installing dependencies via package managers, updating configuration files, and executing lint commands. The security analysis identified a potential surface for indirect prompt injection because the skill processes untrusted project configuration files without explicit sanitization or boundary markers, which could be exploited if those files contain malicious instructions meant to influence the agent's behavior during the migration process.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Migrate to Rslint
Goal
Migrate lint tooling to Rslint with minimal behavior changes and clear validation.
Supported source linters
- ESLint flat config
- Oxlint
Migration principles (must follow)
- Official docs first: use Rslint docs for CLI, config, inline directives, VS Code settings, rules, and presets. Check capabilities against the installed version; historical migration gaps and workarounds are not permanent limitations.
- Smallest-change-first: migrate package, command, config, and editor wiring before changing source files.
- Preserve lint intent: keep supported rule severities/options where Rslint supports them; call out unsupported rules/plugins instead of silently dropping behavior.
- Preserve inline suppression intent: preserve which directives take effect, their rule targets, and their scope. Keep compatible prefixes unless the user requests renaming; translate source-only syntax and account for disabled directive compatibility in the source-specific guide.
- Validate before cleanup: switch lint entry points to Rslint and validate the migrated scope before removing obsolete source-linter artifacts. Report unsupported-rule coverage differences without treating them as a blocker or requiring separate approval.
Workflow
-
Detect source linter
- ESLint flat config:
eslint.config.*,eslintdependency, or package scripts that runeslint. - Oxlint:
.oxlintrc.json,.oxlintrc.jsonc,oxlint.config.*,oxlintdependency, or commands that runoxlint. - Record installed versions, commands, working directories, environment switches, and the scope being migrated. Include shared configs, nested configs, and root fallback behavior within that scope.
- If the source linter is not covered by a reference yet, inventory the current behavior and explain that no dedicated migration reference exists.
- ESLint flat config:
-
Prepare Rslint and apply the source-specific guide
- Select and install the intended
@rslint/coreversion with the repository's package manager before checking its rules, config, and plugin APIs. Respect existing version constraints and retain the source linter for validation. - ESLint flat config: references/eslint-flat-config.md
- Oxlint: references/oxlint.md
- For community or local JS plugins from either source, also read references/eslint-plugins.md.
- Select and install the intended
-
Update lint entry points
- Use a supported
rslint.config.*format. Keep source plugin dependencies required by the translated config. - Update package scripts, CI, hooks, and staged-file commands in the migrated scope. Use the Rslint CLI reference to translate flags while preserving working directories, file arguments, warning thresholds, and environment switches.
- Update existing editor integration using the Rslint VS Code guide. Keep unrelated editor tools and settings.
- Use a supported
-
Validate behavior
- Run the migrated lint command.
- Check effective rules/options, file coverage, suppressions, and plugin execution against the source inventory. A successful exit alone does not establish equivalent behavior.
- For enabled source rules without a validated native or compatible JS-plugin replacement, omit unsupported target keys and record the rule names, affected file scope, and lost coverage for the final report. Continue the migration with the supported rules.
- If the project had a fix command, run the migrated fix command only when appropriate for the task.
- Resolve target config-loading errors, invalid options for supported rules, command failures, and editor-integration errors before cleanup.
-
Cleanup and summarize
- Confirm all lint entry points in the migrated scope use Rslint, then remove obsolete source-linter commands, configuration, and dependencies after validation.
- Summarize the completed switchover and validation, naming any omitted rules/plugins, affected scopes, and coverage or behavior changes.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/rstackjs/agent-skills/migrate-to-rslint">View migrate-to-rslint on skillZs</a>