How do I install the Migrate To Rslint skill?

Run npx skillmds@latest add rstackjs/migrate-to-rslint in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Migrate To Rslint safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Migrate To Rslint?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Migrate To Rslint free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Migrate To Rslint?

rstackjs (@rstackjs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Migrate To Rslint by rstackjs — Agent Skill

Name: Migrate To Rslint
Rating: 4.2 (5 reviews)
Author: rstackjs

Migrate To Rslint

Migrate ESLint or other linters to Rslint. Use when asked to replace ESLint flat config, lint scripts, VS Code ESLint settings, inline directives, rules, presets, plugins, or lint dependencies with Rslint equivalents.

rstackjs 6a74987 2 files · 12.5 KB Updated Sep 9, 2026

File contents

Migrate to Rslint

Goal

Migrate lint tooling to Rslint with minimal behavior changes and clear validation.

Supported source linters

ESLint flat config

Migration principles (must follow)

Official docs first: treat Rslint docs as source of truth for CLI, config, inline directives, VS Code settings, rules, and presets.
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.
Do not rewrite inline directives by default: Rslint supports eslint-disable and rslint-disable; replace prefixes only when the user asks.
Validate before cleanup: keep old linter dependencies/config until the Rslint command passes for the migrated scope, then remove obsolete linter-only artifacts.

Workflow

Detect source linter
- ESLint flat config: eslint.config.*, eslint dependency, or package scripts that run eslint.
- If the source linter is not covered by a reference yet, inventory the current behavior and explain that no dedicated migration reference exists.
Apply source-specific migration guide
- ESLint flat config: references/eslint-flat-config.md
Validate behavior
- Run the migrated lint command.
- If the project had a fix command, run the migrated fix command only when appropriate for the task.
- Resolve config, rule, and editor-setting issues before removing legacy files.
Cleanup and summarize
- Remove obsolete linter dependencies/config after Rslint is green.
- Summarize changed files, migrated presets/plugins, unsupported gaps, and remaining manual follow-ups.

---name: migrate-to-rslintdescription: Migrate ESLint or other linters to Rslint. Use when asked to replace ESLint flat config, lint scripts, VS Code ESLint settings, inline directives, rules, presets, plugins, or lint dependencies with Rslint equivalents.---  # Migrate to Rslint ## Goal Migrate lint tooling to Rslint with minimal behavior changes and clear validation. ## Supported source linters - ESLint flat config ## Migration principles (must follow) 1. **Official docs first**: treat Rslint docs as source of truth for CLI, config, inline directives, VS Code settings, rules, and presets. 2. **Smallest-change-first**: migrate package, command, config, and editor wiring before changing source files. 3. **Preserve lint intent**: keep supported rule severities/options where Rslint supports them; call out unsupported rules/plugins instead of silently dropping behavior. 4. **Do not rewrite inline directives by default**: Rslint supports `eslint-disable` and `rslint-disable`; replace prefixes only when the user asks. 5. **Validate before cleanup**: keep old linter dependencies/config until the Rslint command passes for the migrated scope, then remove obsolete linter-only artifacts. ## Workflow 1. **Detect source linter** - ESLint flat config: `eslint.config.*`, `eslint` dependency, or package scripts that run `eslint`. - If the source linter is not covered by a reference yet, inventory the current behavior and explain that no dedicated migration reference exists. 2. **Apply source-specific migration guide** - ESLint flat config: `references/eslint-flat-config.md` 3. **Validate behavior** - Run the migrated lint command. - If the project had a fix command, run the migrated fix command only when appropriate for the task. - Resolve config, rule, and editor-setting issues before removing legacy files. 4. **Cleanup and summarize** - Remove obsolete linter dependencies/config after Rslint is green. - Summarize changed files, migrated presets/plugins, unsupported gaps, and remaining manual follow-ups.

Frequently asked questions