vscode-rest-client-generator

Generate VS Code REST Client .http files from API route definitions.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/vecear/Nipponverb --skill vscode-rest-client-generator-vecear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-rest-client-generator
Source: https://github.com/vecear/Nipponverb/tree/main/.claude/skills/vscode-rest-client-generator
Command: npx skills add https://github.com/vecear/Nipponverb --skill vscode-rest-client-generator-vecear

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander, and includes scripts (resource) components.

What problem does it solve?

This tool automates the creation of VS Code REST Client .http files from API routes, saving time and eliminating repetitive boilerplate.

Core Features & Use Cases

  • Auto-detect API routes and generate organized .http files or per-resource files.
  • Support environment variables, authentication, and reusable templates for fast testing.
  • Use case: Quickly scaffold HTTP requests for a new API during development or testing.

Quick Start

Run the generator to scan your API routes and produce organized .http files.

Frequently Asked Questions about vscode-rest-client-generator

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

FAQPage Schema
How do I generate VS Code REST Client .http files from Express or Fastify routes?

Generate VS Code REST Client .http files from Express or Fastify routes by scanning API route definitions to produce organized requests with variables, environments, and authentication for inline integration testing.

Can I create separate .http files for each API resource instead of a single file?

You can output per-resource .http files instead of a single file by configuring the generator, which scans API route definitions to produce organized requests with variables, environments, and authentication.

Does the REST Client generator support automatic path parameter replacement for Next.js APIs?

Automatic path parameter replacement is supported for Next.js APIs, producing organized .http requests with JSON bodies, variables, environments, and optional custom headers during integration testing.

What's the best way to scaffold HTTP requests for a new API during development?

Scaffold HTTP requests for a new API by running the generator to scan route definitions, eliminating repetitive boilerplate and producing organized .http files with environment variables and authentication.

Are environment variables and authentication headers included when generating .http files?

Environment variables and authentication are included when generating .http files, supporting reusable templates and automatic path parameter replacement for fast inline API testing.

Do I need the commander dependency to generate .http files from API routes?

Commander is the only dependency required to run the script that scans API route definitions and generates organized VS Code REST Client .http files with JSON bodies and optional custom headers.