you-dont-need-isr

Detect ISR usage in Next.js projects and recommend caching alternatives.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/erezrokah/skills --skill you-dont-need-isr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: you-dont-need-isr
Source: https://github.com/erezrokah/skills/tree/main/skills/you-dont-need-isr
Command: npx skills add https://github.com/erezrokah/skills --skill you-dont-need-isr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes a Next.js project's ISR usage to identify where ISR is applied, how it affects performance and user experience, and whether it is the right fit for the observed routes.

Core Features & Use Cases

  • Detects ISR usage across App Router and Pages Router, including revalidate, next fetch, unstable_cache, and dynamic routing signals.
  • Classifies occurrences with actionable verdicts and suggests simpler or more reliable alternatives like SSR, SSG with webhooks, or on-demand revalidation.
  • Produces a practical remediation plan and a step-by-step path to optimize caching strategy without sacrificing user experience.

Quick Start

Provide a Next.js project directory so the tool analyzes ISR usage and outputs actionable recommendations.

Frequently Asked Questions about you-dont-need-isr

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

FAQPage Schema
How do I audit Next.js ISR usage across my project?

To audit Next.js ISR usage, provide your project directory to scan both App Router and Pages Router patterns. The tool identifies revalidate, fetch with next, unstable_cache, revalidatePath, and dynamic exports, recording each hit to evaluate your caching strategy.

Does this tool detect ISR signals in both App Router and Pages Router?

Yes, it detects ISR signals in both App Router and Pages Router. It scans for revalidate, next fetch configurations, unstable_cache, revalidatePath, and dynamic exports to capture every occurrence across your Next.js codebase.

What's the best way to replace Next.js incremental static regeneration?

The best way to replace Next.js incremental static regeneration is by adopting SSR, SSG combined with webhooks, or on-demand revalidation. The tool provides a structured verdict per ISR occurrence with a practical remediation plan to optimize caching.

When should I not use ISR in a Next.js application?

You should not use ISR when strict data freshness is required or when cache invalidation becomes unpredictable. The tool identifies these occurrences and recommends simpler, more reliable alternatives like SSR or on-demand revalidation to avoid sacrificing user experience.

How do I simplify my Next.js caching strategy?

You can simplify your Next.js caching strategy by following the tool's step-by-step remediation plan. It classifies each ISR usage with actionable verdicts and suggests reliable alternatives to optimize performance without sacrificing user experience.