code-standards-analyzer

What This Skill Does

The Code Standards Analyzer is an evidence-based utility designed to bridge the gap between aspirational documentation and the reality of your codebase. Unlike static linters that enforce external rules, this skill reverse-engineers the actual conventions used in your specific repository. By analyzing existing configuration files (such as ESLint, Prettier, and EditorConfig) alongside empirical data extracted from your source code—like naming patterns, function structure, and import habits—the analyzer generates a 'living' STANDARDS.md. This ensures that new contributors onboard to how the code is actually written today, not how it was imagined three years ago.

Installation

To install this skill, use the OpenClaw CLI in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-code-standards-analyzer

Use Cases

1. Brownfield Onboarding: Rapidly understand the tribal knowledge and style conventions of a legacy project without manually auditing thousands of files.
2. Standards Audit: Periodically verify that your team is adhering to established patterns and identify areas of technical debt.
3. Living Documentation: Automate the creation and maintenance of onboarding materials, ensuring that documentation stays updated as project conventions evolve.
4. Anti-Pattern Detection: Quickly pinpoint high-risk areas, such as excessive 'any' types, large files, or insecure practices that undermine project stability.

Example Prompts

1. 'Analyze the current codebase and generate a STANDARDS.md file that summarizes our naming conventions and file organization.'
2. 'Check if our codebase is following consistent error handling patterns and identify any anti-patterns.'
3. 'What are the implicit naming conventions for functions and classes in this project? Provide examples from the code.'

Tips & Limitations

• Confidence Levels: Pay attention to the statistical confidence provided in the output; the more consistent your code, the higher the confidence.
• Reality Check: Remember that this skill identifies what is, not what should be. If your codebase has poor quality, the generated standards will reflect that. Use it as a starting point for refactoring.
• Performance: While explicit discovery is instantaneous, implicit analysis takes longer (approx 30s) as it performs static analysis across your source files. Run it during dedicated maintenance sessions rather than during tight performance windows.