Generate LPCDoc comment blocks for LPC functions, classes, and modules.
npx skills add https://github.com/gesslar/oxidus-mudlib --skill lpcdoc
Please help me install this Agent Skill. Skill: lpcdoc Source: https://github.com/gesslar/oxidus-mudlib/tree/main/.claude/skills/lpcdoc Command: npx skills add https://github.com/gesslar/oxidus-mudlib --skill lpcdoc
LPCDoc provides a centralized, repeatable standard for documenting LPC functions, classes, and modules, ensuring clear, consistent header comments across a codebase.
Generate a complete LPCDoc comment block for a given function or object, following the documented structure and tag rules.
High-intent search queries and answers about installing and using this skill.
You generate standardized LPC documentation blocks by creating LPCDoc comment headers that enforce required frontmatter, proper tags, and line-length compliance. This ensures consistent documentation structure across your LPC functions, classes, and modules.
The proper format for LPCDoc comment blocks requires a mandatory frontmatter style, essential validation tags, and readable line-length compliant formatting. This standardizes header comments for public functions, typedefs, and properties.
You ensure consistent coding standards for LPC file headers and typedefs by applying LPCDoc templates during code authoring or updates. This guides formatting and validates documentation to improve IDE IntelliSense and maintainability.
Yes, you need to add descriptions for every public LPCDoc block when documenting LPC modules. The system enforces mandatory descriptions for public blocks and validates essential tags to ensure clear, consistent header comments.
You should validate LPCDoc blocks during code authoring or updating, before committing changes. Consulting the documentation standard at this stage ensures your LPC functions and objects meet the required frontmatter and tag rules.
A key limitation of LPCDoc is its strict enforcement of specific required frontmatter and tag rules, meaning non-compliant or custom comment styles will be rejected to maintain readable, line-length compliant blocks across the project.
totvsGenerate ProtheusDOC comment blocks for AdvPL and TLPP source code elements.
korchasaGenerate AI rules for coding standards and IDE-specific file patterns.
kcenonEnforce documentation standards for READMEs, API docs, and code comments.
t-stringsEnforce global-commenting standards across source files and documentation during code reviews.
