editorconfig-linterValidate .editorconfig syntax and check source files for EditorConfig compliance.
Install via ClawdBot CLI:
clawdbot install charlie-morrison/editorconfig-linterGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Sep 29, 2026
A frontend engineering team adds the EditorConfig Linter to their GitHub Actions pipeline to automatically validate .editorconfig files and check all source files for indentation, line endings, and trailing whitespace. Developers get immediate feedback on pull requests, catching style violations before they are merged.
A distributed team working across Windows, macOS, and Linux uses the linter to ensure consistent file formatting after each merge. The tool checks charset, end-of-line, and indent settings, reducing noise in git diffs and preventing merge conflicts caused by inconsistent editors.
An open source maintainer integrates the linter into their contribution workflow to enforce the repository's .editorconfig rules before accepting external pull requests. Contributors can run the fix command locally, and the CI strict mode ensures only compliant code is merged.
A company preparing to onboard a large legacy codebase runs the linter to generate a compliance report, identifying files that violate the project's EditorConfig rules. The JSON output is used to prioritize cleanup sprints and auto-fix simple formatting issues.
A coding bootcamp or online course platform uses the linter to check student submissions against predefined style guides. Instructors can run validate and check commands in an automated grader, teaching students to adhere to professional formatting standards from the start.
The core linter is freely available under an open source license, while a paid support tier offers priority bug fixes, custom rule development, and dedicated integration assistance for enterprise teams. This builds community goodwill while generating revenue from organizations that need reliability and customization.
Offered as a hosted service integrated with popular CI/CD platforms (GitHub Actions, GitLab CI, Jenkins), where teams pay a monthly subscription based on repository count or number of checked files. The SaaS provides dashboards, historical compliance reports, and team management features.
Sell annual enterprise licenses that include the linter plus advanced reporting, audit logs, and integration with internal code review systems. Companies in regulated industries pay for guaranteed compliance evidence and support for custom .editorconfig rule sets.
💬 Integration Tip
Integrate the linter as a pre-commit hook or CI step using the --strict flag to automatically fail builds on violations; use --format json for machine-readable reports in dashboards. Pair it with auto-fix in a nightly job to gradually clean up existing codebases without blocking development.
Scored Sep 29, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.