doc-agent

Generate feature READMEs and CHANGELOG entries from mobile source code.

Updated Aug 27, 2026

Search Tags:#changelog #code analysis #documentation #mobile development #readme generation #feature documentation

Ready to run

npx skills add https://github.com/XiriGo/ecommerce-mobile --skill doc-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-agent
Source: https://github.com/XiriGo/ecommerce-mobile/tree/main/.claude/skills/doc-agent
Command: npx skills add https://github.com/XiriGo/ecommerce-mobile --skill doc-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of comprehensive documentation for new features in the XiriGo Ecommerce mobile application, ensuring consistency and reducing manual effort for developers.

Core Features & Use Cases

Automated Documentation Generation: Writes feature-specific READMEs and updates the CHANGELOG.
Cross-Platform Consistency: Ensures documentation covers both Android and iOS implementations.
Use Case: After a new "Wishlist" feature is developed for both platforms, this Skill can be invoked to generate its documentation, including API details, screen states, and file locations.

Quick Start

Use the doc-agent skill to write documentation for the new user profile feature.

Frequently Asked Questions about doc-agent

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

FAQPage Schema

How do I generate documentation for mobile application features from source code?▼

To generate documentation for mobile application features, you can use an agent that analyzes source code and project standards to automatically write feature READMEs and CHANGELOG entries. It requires access to project overviews, coding standards, and platform-specific source files.

How do I ensure cross-platform documentation consistency for Android and iOS feature releases?▼

Cross-platform documentation consistency for Android and iOS is achieved by analyzing both platform-specific source files against uniform project coding standards. This process generates unified handoff documents and feature READMEs that accurately cover API details and screen states for both implementations.

What is the best way to automate CHANGELOG entries and README generation for new mobile features?▼

Automating CHANGELOG entries and README generation is best handled by an agent that analyzes source code to write feature-specific documentation. This ensures consistent formatting and reduces manual effort by extracting API details, screen states, and file locations directly from the codebase.

Do I need to provide developer handoffs and project standards to generate feature documentation?▼

Yes, you need to provide developer handoffs, project overviews, and coding standards to generate feature documentation. The documentation agent requires these inputs alongside platform-specific source files to accurately map API details, screen states, and file locations for the target feature.

Can I document screen states and file locations for a Wishlist feature across mobile platforms?▼

Yes, you can document screen states and file locations for a Wishlist feature across mobile platforms. By analyzing the Android and iOS source files for the feature, the agent generates comprehensive documentation including API details, screen states, and specific file locations.

What limitations exist when generating documentation for mobile application features?▼

Limitations when generating mobile application feature documentation include the strict requirement for all platform-specific source files and project standards. Without access to complete developer handoffs and coding standards, the agent cannot accurately generate comprehensive feature READMEs or CHANGELOG entries.