Trace git diffs to identify impacted Next.js App Router routes.
npx skills add https://github.com/tonehq/tone --skill find-impacted-routes
Please help me install this Agent Skill. Skill: find-impacted-routes Source: https://github.com/tonehq/tone/tree/main/frontend/.claude/skills/find-impacted-routes Command: npx skills add https://github.com/tonehq/tone --skill find-impacted-routes
Analyzes git diffs between commits to identify which Next.js App Router routes (pages) are affected by code changes. Traces the full impact chain: service changes → Jotai atoms → components → page files → URL routes. Also detects layout changes (affecting all child routes) and middleware changes (affecting all protected routes). Use when the user asks "what routes changed", "which pages are impacted", "what did my diff affect", "find changed pages", "trace route impact", "what routes need testing", or "what pages were modified". Works with the Next.js App Router + Jotai + shadcn/ui frontend in this project.
Run the tool against a frontend git diff to obtain an impact report detailing direct and transitive route changes.
High-intent search queries and answers about installing and using this skill.
Next.js route impact analysis traces code changes from services to page files by building a reverse import graph. It resolves URL routes affected by modified components, atoms, and tools, identifying which specific pages require testing after a commit or branch diff.
Tracing transitive impacts involves parsing TypeScript project files to construct a reverse import graph. This maps how modifications to Jotai atoms and shared components propagate upward through the dependency chain to affect Next.js App Router pages and their URL routes.
Yes, route impact analysis detects Next.js layout and middleware changes. Layout modifications are flagged as affecting all child routes within that directory segment, while middleware changes are identified as impacting all protected routes relying on that middleware logic.
The best way to determine what pages need testing is to generate a structured impact report from the git diff. This report links modified source files to Next.js App Router routes, tracing dependencies through components and atoms to isolate the exact testing scope.
Yes, mapping git diffs to Next.js routes requires a specific frontend stack. The analysis is designed for projects using the Next.js App Router combined with Jotai for state management and shadcn/ui for components to accurately parse and trace the dependency chain.
theslashdojoIdentify and review exact changes across git states with unified diff output.
AgentiveCityAudit accessibility and SEO issues in Next.js App Router projects.
pelithStructures React state with Jotai atoms and derived values for scalable UI.
Siamese001Analyze code impact using AST-based dependency graphs before modifications.
