update-oo-component-documentation

To update object-oriented component documentation after refactoring, this Skill analyzes your source code for structural and API changes, then automatically refreshes Markdown documentation sections including diagrams, interfaces, and implementation details to match the current codebase state.

Yes, this documentation update tool supports language-specific optimizations for C#, Java, TypeScript/JavaScript, and Python components, analyzing code structure and APIs to refresh corresponding documentation accurately for each supported language.

The C4 Model, Arc42, and IEEE 1016 standards provide the structural framework for generating component documentation from code, ensuring that updated Markdown docs include compliant diagrams, interface definitions, and implementation details based on industry best practices.

The best way to keep Markdown documentation synchronized with your object-oriented codebase is to use automated code analysis that extracts component paths, detects structural changes, and regenerates documentation sections directly from the updated source code.

Yes, you can update documentation for a specific component path by providing the source file location, such as 'src/services/userService.cs', and the Skill will analyze that component to refresh its corresponding Markdown documentation.

You should avoid using automated component documentation generation if your codebase lacks existing Markdown documentation to update, as this Skill is designed to refresh and synchronize existing component docs rather than create initial documentation from scratch.