api-documenter

Generate markdown API documentation from route files, controllers, services, and migrations.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dnsnamdang/hrm-claude-config --skill api-documenter-dnsnamdang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-documenter
Source: https://github.com/dnsnamdang/hrm-claude-config/tree/main/nhatlinh/.claude/skills/api-documenter
Command: npx skills add https://github.com/dnsnamdang/hrm-claude-config --skill api-documenter-dnsnamdang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of generating API documentation for endpoints, streamlining the documentation creation for developers and integrators.

Core Features & Use Cases

  • Automated Documentation: Automatically create API specification documents based on existing code.
  • Endpoint Coverage: Covers route files, controllers, services, transformers/resource, and migrations.
  • Use Case: Ideal for documenting API endpoints before development or during code reviews to ensure clarity and accuracy.

Quick Start

Run the skill to generate API documentation for the 'Modules/Order/Routes/api.php' file.

Frequently Asked Questions about api-documenter

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

FAQPage Schema
How do I generate API documentation from existing route files and controllers?

You can generate API documentation by analyzing route files, controllers, services, transformers, and migrations. The tool scans these codebase components to produce a markdown document detailing endpoint methods, request/response formats, and business logic.

What is automated API specification generation and how does it work?

Automated API specification generation analyzes your source code to extract endpoint definitions and business logic. It processes route files and controllers to output a markdown document covering endpoint methods, request formats, and response structures.

Can I document endpoint methods and request/response formats for code reviews?

Yes, you can document endpoint methods and request/response formats during code reviews. The process analyzes controllers and migrations to ensure clarity and accuracy before development or during review stages.

Does automated endpoint documentation work with services and transformers?

Automated endpoint documentation works with services and transformers by analyzing them alongside route files and controllers. It extracts business logic and data transformation rules to include in the generated markdown specification.

What is the best way to automate markdown documentation for API endpoints?

The best way to automate markdown documentation for API endpoints is using code analysis on route files and migrations. This approach directly extracts methods and request/response formats to generate accurate markdown specifications without manual entry.

What are the limitations of code analysis for generating API documentation?

Code analysis for generating API documentation is limited to the logic explicitly defined in route files, controllers, and migrations. It may not capture external API behaviors or runtime configurations not present in the analyzed source code.