Agent skill · software engineering · aiskillstore
code-style-enforcer
Analyzes code for style consistency and applies project-specific formatting conventions beyond what linters catch. Use when reviewing code, ensuring style consistency, or when user requests code style improvements.
Why this skill is useful
Adds project-specific style analysis commands and conventions that automated linters may miss.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 STYLEGUIDE.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, snakecase) Import/export organization Code structure: Class/function ordering Public vs private method placement Constant/variable declaration location Formatting: Indentation (spaces vs tabs, size) Line length limits Blank line usage Comment styles Naming: Variable naming (camelCase, snakecase) Class naming (PascalCase, capitalization) Constant naming (UPPERCASE, etc.) File naming patterns Use Grep to find common patterns across similar files. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/code-style-enforcer