understand

You can name Melee decompilation functions by analyzing usage patterns and applying descriptive identifiers with module prefixes. The Skill renames address-based functions like ftCo_8007E3B0 to ftCo_Shield_CalcDamage, preserving original addresses when necessary.

The best way to document struct fields in Melee decompilation is to name them based on usage patterns and add @brief-style notes with @param-like annotations where applicable, improving readability and discoverability across function-level and file-level usages.

Yes, you can automatically generate documentation for reverse-engineered Melee code. The Skill applies @brief descriptions and @param annotations to functions and struct fields, allowing you to describe a target once and generate context notes for the chosen symbol or file.

Yes, naming Melee decompilation symbols requires preserving address-based names when necessary. The Skill ensures new descriptive identifiers follow module prefixes but retains original address-based names to maintain compatibility within dedicated worktrees.

To apply consistent naming conventions across a Melee codebase module, generate naming and documentation that follows module prefixes at the function-level, file/module-level, and struct-field usages within dedicated worktrees for improved code readability.