route-scanning
Route-scanning analyzes Express.js source directories to extract all API route definitions, including HTTP methods, paths, file locations, line numbers, applied middleware, and route type classifications. Use this skill when building API documentation, generating route inventories, or preparing route data for downstream processing pipelines that require structured endpoint information.
git clone --depth 1 https://github.com/huangjia2019/claude-code-engineering /tmp/route-scanning && cp -r /tmp/route-scanning/04-Skills/projects/08-skill-pipeline/.claude/skills/route-scanning ~/.claude/skills/route-scanningSKILL.md
# 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).Review code changes for quality, security, and best practices. Proactively use this after code modifications.
Run tests and report results concisely. Use this after code changes to verify everything works.
Analyze log files and extract actionable insights. Use when troubleshooting issues or investigating incidents.
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.
Explore and analyze database-related code. Use when investigating data models, queries, or persistence.
Analyze root cause of bugs after location is identified. Second step in bug investigation.
Implement bug fixes after analysis is complete. Third step in bug fix pipeline.