Wheels Documentation Generator

Generate CFML documentation, READMEs, and API docs for CFWheels applications.

203|108|Updated Jan 13, 2011
One-click install
npx skills add https://github.com/wheels-dev/wheels --skill wheels-documentation-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Wheels Documentation Generator
Source: https://github.com/wheels-dev/wheels/tree/main/.claude/skills/wheels-documentation-generator
Command: npx skills add https://github.com/wheels-dev/wheels --skill wheels-documentation-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of consistent and comprehensive documentation for CFWheels applications, including function comments, model descriptions, and project README files. It ensures your codebase is well-documented, making it easier for teams to understand, maintain, and onboard new developers.

Core Features & Use Cases

  • Function Documentation: Provides templates for JSDoc-style comments for functions, including @param and @return tags.
  • Model Documentation: Guides on documenting model associations, validations, and overall purpose.
  • README Template: Generates a standard project README.md file with sections for description, requirements, installation, configuration, and testing.
  • Use Case: Document your authenticate function in a User model. This skill provides the correct JSDoc-style comment structure, including @param and @return tags, making your code easier to understand and maintain for anyone working on the project.

Quick Start

/**

  • Authenticate user with email and password
  • @param email User's email address
  • @param password User's password (plain text)
  • @return User object if authenticated, false otherwise */ public any function authenticate(required string email, required string password) {

    ...

}

Frequently Asked Questions about Wheels Documentation Generator

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

FAQPage Schema
How do I generate documentation for my Wheels project?

Generate documentation by extracting function signatures, parameters, and return values from your Wheels codebase, then render them into JSDoc-style CFML comments, Markdown README files, and API documentation. This automates consistent documentation across authentication, models, associations, validations, and deployment steps.

What should a documented Wheels function look like?

A documented Wheels function includes JSDoc-style comments with `@param` tags for each parameter and `@return` tags describing the output. For example, an authenticate function documents email and password parameters plus the User object or false return value, making code intent clear for team members.

Can I document Wheels model associations and validations?

Yes. This Skill captures model associations, validations, and overall purpose, then renders them into standardized documentation. It guides documenting relationships between models and validation rules, ensuring your data layer is transparent to developers maintaining the codebase.

Does this generate a README file for my Wheels project?

Yes. The Skill generates a standard README.md template with sections for project description, requirements, installation, configuration, and testing. This provides new team members and collaborators with onboarding documentation covering setup and key workflows.

What parts of a Wheels codebase can be documented?

Documentation covers function-level docs with parameter and return types, model schemas including associations and validations, and project-wide README files. This applies across authentication systems, data models, business logic, and deployment procedures.

Why is consistent code documentation important for Wheels teams?

Consistent documentation using JSDoc-style comments and standardized READMEs reduces onboarding time, improves code maintainability, and prevents knowledge silos. Teams understand function purposes, parameter requirements, and project structure without reverse-engineering the codebase.