route-scanning

Solid

Scan Express.js source files to discover all API route definitions.

API & Backend 1,024 stars 365 forks Updated 5 days ago

Install

View on GitHub

Quality Score: 84/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
41
Issue Health 10%
50
License 10%
0
Description 5%
100

Skill Content

# Route Scanning Skill Discover all API route definitions in Express.js source files. ## Process ### Step 1: Run Route Scanner Execute the scanning script: ```bash python3 scripts/scan-routes.py <source_directory> ``` The script outputs a structured route list with method, path, file, and line number. ### Step 2: Enrich Route Data For each discovered route, also identify: - Middleware applied (auth, validation, etc.) - Whether it's a standard route or chained route (`router.route()`) ### Output Format Return a JSON-compatible route manifest: ```json [ { "method": "GET", "path": "/api/products", "file": "src/routes/products.js", "line": 8, "middleware": ["requireAuth"], "type": "standard" } ] ``` This manifest will be consumed by the next pipeline stage (doc-writing).

Details

Author
huangjia2019
Repository
huangjia2019/claude-code-engineering
Created
6 months ago
Last Updated
5 days ago
Language
JavaScript
License
None

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Solid

api-generating

Generate API endpoint documentation from Express route files. Use when the user asks to generate, update, or review API docs for Express.js routes.

1,024 Updated 5 days ago
huangjia2019
API & Backend Listed

api-surface

Maps the entire API surface of a codebase -- route definitions, middleware chains, auth requirements, request/response types, deprecated endpoints, orphaned endpoints, and cross-endpoint inconsistencies. USE THIS SKILL WHEN: - You need a complete inventory of all API endpoints in a project - Someone asks "what endpoints do we have?" or "what does our API look like?" - You are onboarding to a new backend codebase and need to understand its API - You need to find orphaned, undocumented, or deprecated endpoints - Someone asks about API inconsistencies (different response shapes, auth gaps) - You are preparing for an API review, documentation sprint, or versioning migration - You need to understand endpoint dependencies before refactoring - A project has no OpenAPI spec and you need to generate one from code - You suspect there are endpoints without authentication or rate limiting TRIGGER PHRASES: "API surface", "list all endpoints", "API inventory", "endpoint map", "orphaned endpoints", "API inconsistencies", "u

8 Updated 1 weeks ago
tinh2
API & Backend Listed

route-auth-sweep

Enumerate every API route and prove each one gates before it touches data — authentication, ownership checks, role checks, rate limiting — so no endpoint is accidentally public or leaks another user's records. Use before a launch, after adding routes, during a security review, or when the user asks whether their API is safe.

0 Updated today
sriptcollector