Route Research for Testing

Extract edited route paths from tsc-cache logs into JSON test specifications.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill route-research-for-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Route Research for Testing
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-condensed/route-research-for-testing
Command: npx skills add https://github.com/joshka0/foxctl --skill route-research-for-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly identify which API routes were edited and systematically generate test inputs so you can validate both valid and invalid payload shapes without manually chasing changes.

Core Features & Use Cases

  • Changed route discovery: Reads edited route paths from the Claude TypeScript tsc-cache logs and filters for route changes.
  • Request/response shape synthesis: Produces JSON output per route describing method, path, and expected request/response structure, including valid and invalid payloads.
  • Targeted test execution: Triggers the route-tester sub-agent (auth-route-tester) to run tests for the identified routes.

Quick Start

Ask your AI agent to run the Route Research for Testing skill to map the edited routes from your latest tsc-cache and start route tests for them.

Frequently Asked Questions about Route Research for Testing

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

FAQPage Schema
How do I generate API validation tests for changed routes automatically?

To generate API validation tests for changed routes, this skill extracts edited route file paths from Claude tsc-cache logs, applies deterministic filtering and prefix resolution, then emits JSON specifications with valid and invalid payload cases.

How do I map edited application routes to JSON test specifications?

You can map edited application routes to JSON test specifications by reading changed route file paths from tsc-cache logs, applying argument-merging and prefix resolution, then outputting per-route method, path, and request/response shape details.

Can I trigger multi-agent orchestration to run route tests after generating fixtures?

Yes, the skill triggers the auth-route-tester sub-agent for multi-agent orchestration to execute targeted tests for the identified routes after generating the JSON fixtures.

Does this route testing approach work with routes modified under src/app.ts?

Yes, this route testing approach specifically applies when routes under src/app.ts are modified, capturing those edited file paths to focus the generated test specifications on the changed API endpoints.

What are the limitations of using tsc-cache logs for route change discovery?

Route change discovery depends on tsc-cache logs containing edited file paths, meaning it cannot identify route changes if the cache logs are missing, cleared, or if route modifications exist outside the deterministic filter scope.