api-smoke-testing

Discover API endpoints from codebases and test them with HTTP requests.

672|104|Updated Apr 10, 2026

Search Tags:#testing #debugging #api #routing #http #endpoints #smoke test

Ready to run

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill api-smoke-testing-spencerpauly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-smoke-testing
Source: https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/api-smoke-testing
Command: npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill api-smoke-testing-spencerpauly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds every API route in a project and checks whether each endpoint responds correctly, eliminating manual spot checks and making broken routes obvious.

Core Features & Use Cases

Route Discovery: Scans common frameworks such as Next.js, Express, Django, FastAPI, and Rails to build an endpoint list.
Endpoint Validation: Sends HTTP requests to each route and classifies healthy responses, auth-gated routes, redirects, bad requests, and failures.
Debugging Workflow: Helps developers catch 404s and 500s quickly, then trace missing mounts or server-side errors for repair.

Quick Start

Ask the skill to discover the app’s API routes, start the server if needed, and smoke test every endpoint for errors.

Frequently Asked Questions about api-smoke-testing

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

FAQPage Schema

How do I smoke test API endpoints in my codebase?▼

To smoke test API endpoints, this skill discovers routes from your codebase and sends HTTP requests to each one, classifying responses as healthy, auth-gated, redirects, or failures to identify broken routes fast.

How do I find all API routes in a Next.js or Express project?▼

Finding API routes in Next.js, Express, Django, FastAPI, and Rails projects is handled by the route discovery feature, which scans the codebase to build a complete endpoint list for testing and debugging.

How do I debug 404 and 500 errors on my API routes during development?▼

Debugging 404 and 500 responses involves classifying endpoint failures after HTTP requests, tracing missing mounts or server-side errors to the root cause for repair during development and release verification.

Can I use this API smoke testing approach with Django and FastAPI projects?▼

Yes, API smoke testing supports Django and FastAPI projects, scanning their codebases to discover endpoints and validate HTTP responses to catch broken routes during development and release verification.

What is the best way to automate checking server availability before testing API routes?▼

The best way to check server availability is using the endpoint validation workflow, which requires server availability checks before sending HTTP requests to classify each route's status and identify failures.

Why does my API endpoint return a 404 during smoke testing?▼

A 404 response during API smoke testing indicates a missing route mount, which the debugging workflow traces by inspecting the codebase route discovery results to find the root cause of the endpoint failure.