code-style-enforcerlisted

# Code Style Enforcer This skill ensures code follows project-specific style conventions and patterns that automated linters may miss. ## When to Use This Skill - User requests code style review or improvements - Ensuring consistency across the codebase - Onboarding new code or contributors - Pre-commit code review - User mentions "style", "consistency", "formatting", or "conventions" ## Instructions ### 1. Detect Project Style Guides Look for style configuration files: **JavaScript/TypeScript:** - `.eslintrc.*` - ESLint configuration - `.prettierrc.*` - Prettier configuration - `tsconfig.json` - TypeScript compiler options - `.editorconfig` - Editor configuration **Python:** - `.pylintrc`, `pylint.cfg` - Pylint - `pyproject.toml` - Black, isort configuration - `.flake8` - Flake8 configuration - `setup.cfg` - Various tool configs **Ruby:** - `.rubocop.yml` - RuboCop configuration **Go:** - `go.fmt` enforced (standard) - `.golangci.yml` - GolangCI-Lint **Java:** - `checkstyle.xml` - Checkstyle - `.editorconfig` **General:** - `CONTRIBUTING.md` - Contribution guidelines - `STYLE_GUIDE.md` - Project style guide - `.editorconfig` - Cross-editor settings Use Glob to find these files and Read to understand the project's style preferences. ### 2. Analyze Existing Code Patterns Sample existing code to understand implicit conventions: **File organization:** - Directory structure patterns - File naming conventions (camelCase, kebab-case, snake_case) - Import/export orga