adk-unit-guide

Generate structured Markdown guides for code units from source files and tests.

Updated Jul 23, 2026

Search Tags:#documentation #code-analysis #adk #software-engineering #technical-writing #developer-experience

Ready to run

npx skills add https://github.com/rahulgupta2018/agent-skills --skill adk-unit-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adk-unit-guide
Source: https://github.com/rahulgupta2018/agent-skills/tree/main/skills/adk-unit-guide
Command: npx skills add https://github.com/rahulgupta2018/agent-skills --skill adk-unit-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the documentation gap between high-level developer manuals and raw source code by generating granular, technical guides for specific code units.

Core Features & Use Cases

Automated Documentation: Creates detailed guides explaining the purpose, dependencies, and implementation of new or updated code units.
Incremental Updates: Updates existing guides while preserving historical content to ensure documentation stays current with code changes.
Use Case: When a developer introduces a complex new utility class, this skill generates a guide that explains its internal logic, configuration options, and usage patterns for other team members.

Quick Start

Use the adk-unit-guide skill to generate a technical guide for the provided source code file and save it to the docs directory.

Frequently Asked Questions about adk-unit-guide

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

FAQPage Schema

How do I generate technical documentation for specific code units?▼

To generate technical documentation for specific code units, the skill analyzes source code files, design documents, and unit tests to produce structured Markdown guides explaining implementation logic and dependencies.

What is the best way to automate code documentation for developer onboarding?▼

Automating code documentation for developer onboarding is achieved by analyzing source files and unit tests to create granular Markdown guides that explain purpose, configuration, and usage patterns for new team members.

Can I update existing technical guides without losing historical content?▼

Updating existing technical guides without losing historical content is supported through incremental updates, which preserve previous documentation while reflecting current code changes to maintain an accurate knowledge base.

Does the generated documentation integrate with my repository's docs directory?▼

The generated documentation integrates with your repository's docs directory, requiring this connection to maintain an indexed and categorized knowledge base for the structured Markdown guides.

What source files are needed to produce structured Markdown guides for code analysis?▼

Producing structured Markdown guides for code analysis requires source code files, design documents, and unit tests, which are parsed to explain the internal logic and configuration of the target code unit.