fix-eslint

Migrate deprecated navigation type references for React Navigation v7 compatibility.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill fix-eslint-edgeapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-eslint
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/fix-eslint
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill fix-eslint-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves complex TypeScript deprecation warnings, specifically targeting NavigationBase and RouteProp, which are common blockers during React Navigation migrations.

Core Features & Use Cases

  • Automated Refactoring: Provides structured patterns to replace deprecated navigation types with modern alternatives like useNavigation hooks or callback inversion.
  • Safety Verification: Enforces mandatory post-fix type checking to ensure no regressions are introduced during the migration process.
  • Use Case: When your project reports @typescript-eslint/no-deprecated warnings for NavigationBase, use this skill to systematically identify the usage category and apply the appropriate migration pattern.

Quick Start

Use the fix-eslint skill to identify and resolve all deprecated NavigationBase and RouteProp type references in the current codebase.

Frequently Asked Questions about fix-eslint

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

FAQPage Schema
How do I fix TypeScript deprecation warnings for React Navigation v7 migration?

To fix TypeScript deprecation warnings during React Navigation v7 migration, apply standardized refactoring patterns to replace deprecated NavigationBase and RouteProp types with modern alternatives like useNavigation hooks or callback inversion.

What is the best way to refactor deprecated NavigationBase types in TypeScript?

The best way to refactor deprecated NavigationBase types is to systematically identify their usage category and apply structured migration patterns to replace them with modern alternatives like useNavigation hooks.

How do I resolve @typescript-eslint/no-deprecated warnings for RouteProp references?

Resolve @typescript-eslint/no-deprecated warnings for RouteProp references by replacing them with standardized migration patterns and enforcing strict post-fix type compilation checks to prevent regressions.

Can I suppress TypeScript deprecation warnings instead of refactoring navigation types?

No, you cannot suppress TypeScript deprecation warnings as a workaround because this migration approach prohibits warning suppression and enforces strict type safety by requiring post-fix compilation checks.

Does fixing ESLint deprecation warnings require type checking after applying migration patterns?

Yes, fixing ESLint deprecation warnings requires mandatory post-fix type checking because the migration process enforces strict type safety to ensure no regressions are introduced when updating navigation-related type references.

When do I need to migrate edge-react-gui components for React Navigation compatibility?

You need to migrate edge-react-gui components for React Navigation compatibility when your project reports @typescript-eslint/no-deprecated warnings targeting shared services and components requiring updates for React Navigation v7.