← Back to Skills Marketplace

Editorconfig Linter

Name: Editorconfig Linter
Author: charlie-morrison

by charlie-morrison · GitHub ↗ · v1.0.0 · MIT-0

cross-platform ✓ Security Clean

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install editorconfig-linter

Description

Validate .editorconfig syntax and check source files for EditorConfig compliance.

README (SKILL.md)

EditorConfig Linter

Validate .editorconfig files and check source files for compliance.

Commands

Validate .editorconfig syntax

python3 scripts/editorconfig-linter.py validate .editorconfig

Check files against .editorconfig rules

python3 scripts/editorconfig-linter.py check src/
python3 scripts/editorconfig-linter.py check src/ --editorconfig .editorconfig

Show effective config for a file

python3 scripts/editorconfig-linter.py show src/main.py

Fix violations automatically

python3 scripts/editorconfig-linter.py fix src/

Options

--editorconfig PATH — Path to .editorconfig (default: auto-discover)
--format text|json|markdown — Output format (default: text)
--strict — Exit 1 on any violation (CI mode)
--exclude PATTERN — Glob pattern to exclude (repeatable)
--max-files N — Max files to check (default: 1000)

What It Checks

.editorconfig Syntax

Invalid property names
Invalid property values (indent_style must be tab/space, etc.)
Duplicate sections
Unreachable sections (shadowed by earlier glob)
Missing root = true
Invalid glob patterns

File Compliance (9 rules)

indent_style — tabs vs spaces
indent_size — number of spaces per indent
end_of_line — lf, crlf, cr
charset — utf-8, utf-8-bom, latin1, utf-16be, utf-16le
trim_trailing_whitespace — trailing whitespace check
insert_final_newline — file ends with newline
max_line_length — line length limit
tab_width — tab display width
Mixed indentation detection

Exit Codes

0: No violations
1: Violations found (or --strict)
2: Invalid arguments or .editorconfig errors

Usage Guidance

This skill appears to do what it claims: parse .editorconfig, report violations, and optionally auto-fix issues. Before running: (1) inspect the full scripts/editorconfig-linter.py file locally (the provided listing in this review is truncated near the end); (2) run 'validate' and 'check' first to see issues, and back up your repository or use version control before using 'fix' since it can modify files; (3) run it on a small test directory or in a sandbox to confirm behavior (line-ending and BOM fixes can alter many files); (4) if you need absolute assurance, open the rest of the script to confirm there are no network calls or unexpected filesystem operations beyond the stated checks and fixes.

Capability Analysis

Type: OpenClaw Skill Name: editorconfig-linter Version: 1.0.0 The skill bundle provides a standard EditorConfig linter and fixer implemented in Python using only the standard library. The code in scripts/editorconfig-linter.py performs file system operations (reading and writing) consistent with its stated purpose of validating and fixing file formatting, with no evidence of data exfiltration, malicious execution, or prompt injection.

Capability Assessment

✓ Purpose & Capability

Name/description (EditorConfig linter) match the included artefacts: SKILL.md documents validate/check/show/fix commands and the bundle includes a Python script implementing parsing and file checks. No unrelated env vars, binaries, or installs are requested.

ℹ Instruction Scope

SKILL.md instructs the agent to run the bundled Python script against project files (e.g., python3 scripts/editorconfig-linter.py check src/). The script legitimately reads repository files to check compliance and supports a 'fix' command that will modify files — this is expected for an auto-fixer but is a potentially impactful operation the user should run on backed-up or non-sensitive data first.

✓ Install Mechanism

No install spec; the skill is instruction-only with a bundled Python script relying only on the stdlib. This is low-risk compared with remote downloads or package installs.

✓ Credentials

The skill declares no required environment variables, credentials, or config paths. The script operates on files passed as arguments and does not import networking or credential-handling libraries, so requested access is proportionate to its purpose.

✓ Persistence & Privilege

always is false and model invocation is allowed (platform default). The skill does not request permanent system-wide changes, nor does it try to modify other skills or agent configuration according to the provided files.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install editorconfig-linter
After installation, invoke the skill by name or use /editorconfig-linter
Provide required inputs per the skill's parameter spec and get structured output

Version History

v1.0.0

Initial release

Metadata

Slug editorconfig-linter

Version 1.0.0

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 1

Frequently Asked Questions

What is Editorconfig Linter?

Validate .editorconfig syntax and check source files for EditorConfig compliance. It is an AI Agent Skill for Claude Code / OpenClaw, with 88 downloads so far.

How do I install Editorconfig Linter?

Run "/install editorconfig-linter" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Editorconfig Linter free?

Yes, Editorconfig Linter is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Editorconfig Linter support?

Editorconfig Linter is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Editorconfig Linter?

It is built and maintained by charlie-morrison (@charlie-morrison); the current version is v1.0.0.

More Skills