lint-rules

Detect vague language, conflicts, and redundancies in instruction files.

71|7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mbwsims/claude-universe --skill lint-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-rules
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/lint-rules
Command: npx skills add https://github.com/mbwsims/claude-universe --skill lint-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lint Instructions analyzes instruction files for quality issues: vague rules, conflicts, redundancies, and misplacements, and provides structured guidance to improve clarity, consistency, and safety.

Core Features & Use Cases

  • Detect vague language, conflicts, and redundancies in CLAUDE.md and related rule files.
  • Propose concrete rewrites, metadata fixes, and consolidation opportunities.
  • Generate an actionable improvement plan including coverage gaps and token-budget guidance.

Quick Start

Run the lint workflow to scan CLAUDE.md and related rules and receive concrete rewrite recommendations.

Frequently Asked Questions about lint-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect vague language and conflicts in CLAUDE.md instruction files?

To detect vague language and conflicts in CLAUDE.md instruction files, you can run a linting workflow that scans for quality issues like redundancies and misplacements, providing structured guidance to improve clarity and safety.

What is the best way to consolidate overlapping rules in CLAUDE.md?

The best way to consolidate overlapping rules in CLAUDE.md is to use a linting tool that identifies redundancies and provides concrete rewrite recommendations alongside consolidation opportunities tailored to your project's context.

How do I get actionable rewrites for vague instructions in my rule files?

You can get actionable rewrites for vague instructions by analyzing your rule files with a linter, which proposes concrete rewrites, metadata fixes, and an improvement plan with token-budget considerations.

Can I check CLAUDE.md files for token-budget considerations and coverage gaps?

Yes, you can check CLAUDE.md files for token-budget considerations and coverage gaps by running a lint workflow that generates an actionable improvement plan highlighting these specific issues.

Why does my CLAUDE.md have conflicting instructions and how do I fix them?

Conflicting instructions in CLAUDE.md occur when rules contradict each other or are misplaced, and you can fix them by running a deterministic linter to identify the exact conflicts and receive targeted rewrite suggestions.

Are there limitations to deterministic linting for CLAUDE instructions?

Deterministic linting for CLAUDE instructions relies on analyzing existing file content for vague language and conflicts, meaning it cannot infer implicit project requirements that are not explicitly documented within the instruction files themselves.