How do I install the J5ik2o Custom Linter Creator skill?

Run npx skillmds@latest add j5ik2o/j5ik2o-custom-linter-creator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is J5ik2o Custom Linter Creator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with J5ik2o Custom Linter Creator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is J5ik2o Custom Linter Creator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published J5ik2o Custom Linter Creator?

j5ik2o (@j5ik2o) published this skill. Their other Agent Skills are listed on their SkillMD profile.

J5ik2o Custom Linter Creator by j5ik2o

Name: J5ik2o Custom Linter Creator
Author: j5ik2o

J5ik2o Custom Linter Creator

Use when creating project-specific lint rules for AI agents or humans using existing language linter ecosystems. Generates rules under a `lints/` directory with actionable diagnostic messages that tell an agent exactly how to repair the violation. Trigger for custom lint rules, AI linter rules, enforcing naming or structure patterns, or turning code-review rules into lint checks.

j5ik2o Updated Sep 17, 2026

File contents

Custom Linter Creator

Prefer the host language's existing linter ecosystem. The diagnostic message is part of the design: it should be a repair prompt, not just a complaint.

Workflow

Extract the rule as a precise, statically detectable condition.
Pick the native ecosystem: ESLint for TypeScript/JavaScript, pylint for Python, Go analysis/golangci-lint for Go, dylint or Clippy-style tooling for Rust.
Create the rule under lints/ with tests or fixtures.
Write diagnostics that include the violation, repair steps, scope limits, and rationale.
Integrate the rule into the project lint command.

Diagnostic Template

Use this shape: Problem: ... Repair: 1. ... 2. ... Scope: ... Rationale: ....

Reference

Read references/language-ecosystems.md for ecosystem-specific scaffolding.

Detailed Reference

For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.

Output

Return the rule definition, file layout, diagnostic text, test fixture, and command to run it.

Frequently asked questions