port-rule

Migrate ESLint rules to rslint with a complete porting workflow.

433|25|Updated Jul 14, 2025
One-click install
npx skills add https://github.com/web-infra-dev/rslint --skill port-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: port-rule
Source: https://github.com/web-infra-dev/rslint/tree/main/agents/port-rule
Command: npx skills add https://github.com/web-infra-dev/rslint --skill port-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Porting ESLint rules to rslint is time-consuming and error-prone when done manually. This skill provides a repeatable workflow to port rules from ESLint to rslint, from initial planning through PR submission.

Core Features & Use Cases

  • End-to-end porting workflow: from setup to PR submission.
  • Rule origin analysis and parity verification across core ESLint, TypeScript-ESLint, and plugin rules.
  • Collaborative planning and documentation: gather tests, docs, and integration steps; supports batch porting.

Quick Start

Start by invoking the port-rule skill, supply one or more ESLint rule names, and follow the guided workflow from setup to PR submission.

Frequently Asked Questions about port-rule

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

FAQPage Schema
How do I port an ESLint rule to rslint?

Porting ESLint rules to rslint involves a complete workflow from planning to PR submission. You must supply documentation, tests, and integration steps while enforcing 1:1 parity with the original ESLint behavior using Go-based templates.

Can I batch port multiple ESLint plugin rules to rslint at once?

Yes, batch porting ESLint rules to rslint is supported. The workflow handles collaborative planning, gathers required tests and docs, and manages integration steps across large codebases for bulk rule migration.

Does the rslint porting workflow support TypeScript-ESLint rules?

Yes, the rslint porting workflow supports TypeScript-ESLint rules. It performs rule origin analysis and parity verification across core ESLint, TypeScript-ESLint, and various plugins to ensure accurate migration.

What do I need to migrate an ESLint rule to rslint successfully?

Migrating an ESLint rule to rslint requires you to supply documentation, tests, and integration steps. The workflow enforces 1:1 behavioral parity and uses Go-based rule templates to complete the PR submission.

What is the best way to ensure 1:1 parity when porting ESLint rules to rslint?

The best way to ensure 1:1 parity when porting ESLint rules to rslint is using an automated porting workflow that performs rule origin analysis and verifies behavioral matching from initial planning through PR submission.