api-doc-generation

Generate API documentation from NestJS controllers by parsing decorators and DTOs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill api-doc-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-doc-generation
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/api-doc-generation
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill api-doc-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your API documentation accurately reflects the current state of your NestJS controllers, preventing outdated or misleading information.

Core Features & Use Cases

  • Automated Documentation Updates: Generates and updates API documentation directly from NestJS controller code.
  • Synchronization: Keeps API documentation in sync with controller modifications, endpoint additions, and DTO changes.
  • Use Case: After adding a new endpoint to the products controller, this Skill automatically updates the docs/technical/backend/api/ directory with the new endpoint's details, including parameters, responses, and authentication requirements.

Quick Start

Run the api-doc-generation skill to update the API documentation based on recent controller changes.

Frequently Asked Questions about api-doc-generation

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

FAQPage Schema
How do I generate API documentation from NestJS controllers automatically?

You can generate API documentation from NestJS controllers automatically by parsing decorators and DTOs. This process analyzes endpoints, parameters, request/response schemas, authentication, and status codes to create accurate RESTful API docs.

Why does my API documentation keep getting outdated after modifying NestJS controllers?

API documentation becomes outdated because manual updates lag behind controller modifications. Automating documentation generation directly from NestJS controller code ensures synchronization with endpoint additions, DTO changes, and parameter updates.

What's the best way to keep REST API docs in sync with code changes?

The best way to keep REST API docs in sync with code is to generate them directly from controller logic. By parsing decorators and DTOs from NestJS controllers, documentation automatically reflects endpoint modifications and schema updates.

Can I extract request and response schemas from DTOs for API documentation?

Yes, you can extract request and response schemas from DTOs for API documentation. By leveraging file analysis tools to comprehensively parse NestJS DTOs, the documentation process captures detailed schemas, parameters, and authentication requirements.

Does automated documentation generation work with existing NestJS controller decorators?

Automated documentation generation works with existing NestJS controller decorators by parsing them directly. It analyzes your current codebase to extract endpoints, parameters, and status codes without requiring you to rewrite your controller logic.