qa-pathfinder

Trace HTTP endpoints and frontend routes to generate PATHS.md and pytest stubs.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill qa-pathfinder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-pathfinder
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.agent/skills/qa-pathfinder
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill qa-pathfinder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map all user paths in a web application by reading its source code and API routes, then generate a PATHS.md coverage map and test stubs.

Core Features & Use Cases

  • Discover frontend routes by analyzing source code and routing declarations.
  • Identify backend API endpoints and document the interactions between frontend and backend.
  • Generate PATHS.md with frontend routes, API endpoints, user paths, and accompanying pytest stubs for coverage assessment.
  • Support multiple frontends/backends and produce a structured outline that guides manual QA and automated tests.

Quick Start

Use qa-pathfinder on your project to generate PATHS.md and test stubs from code and live endpoints.

Frequently Asked Questions about qa-pathfinder

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

FAQPage Schema
How do I map all user paths and API endpoints in a web application?

To map user paths in a web application, you analyze source code and trace HTTP endpoints to identify frontend routes and backend APIs, generating a structured PATHS.md coverage map. This process also produces pytest test stubs for coverage assessment.

What is a PATHS.md file and when do I need it for QA testing?

A PATHS.md file documents all discoverable frontend routes, API endpoints, and user paths within a web application. You need it to guide manual QA testing and provide structured outlines for automated test coverage assessment.

How to generate test stubs from source code and live API endpoints?

Generate test stubs by scanning source code routing declarations and performing health checks on live API endpoints. This produces pytest stubs alongside a PATHS.md file to assess test coverage for traced user paths.

Does path discovery work with SPA frameworks and microservices architectures?

Path discovery works with SPA frameworks and microservices by analyzing distinct frontend routes and backend APIs. It supports applications with multiple frontend-backend boundaries to document interactions across separate services.

What's the best way to document interactions between multiple frontends and backends?

Document interactions between multiple frontends and backends by tracing HTTP endpoints and analyzing source code. This generates a PATHS.md file that outlines user paths and API endpoint mappings across all frontend-backend boundaries.

Why does automated path documentation require executing code and scanning routes?

Automated path documentation requires executing code and scanning routes to accurately discover live HTTP endpoints and verify routing declarations. This ensures the generated PATHS.md and test stubs reflect the actual application behavior.