Scan Express.js source files to discover all API route definitions.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill route-scanning --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Route Scanning?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-route-scanning)More formats (shields.io, HTML) on the badges page.
---
name: route-scanning
description: Scan Express.js source files to discover all API route definitions.
allowed-tools: [Read, Grep, Glob, Bash(python3 *)]
---
# 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).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...