OpenSkillIndex← back to search
claude-codedevelopment

Claude-skill-registry lint-code

Check code for style and quality issues. Use when validating code before commits.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/lint-code" ~/.claude/skills/majiayu000-claude-skill-registry-lint-code && rm -rf "$T"
manifest: skills/data/lint-code/SKILL.md
tags
#code-analysis#linting#code-quality#static-analysis#programming
source content

Lint Code

Run linting tools to identify style issues, potential bugs, and code quality problems in source files.

When to Use

  • Pre-commit code validation
  • Finding simple mistakes (unused variables, typos)
  • Enforcing style consistency
  • Quick code review before merging

Quick Reference

# Python linting
pylint module.py
flake8 .
black --check .  # Format checker

# Mojo formatting (enforced by pre-commit)
pixi run mojo format file.mojo

# All linters via pixi
pixi run quality-run-linters

Workflow

  1. Select linters: Choose appropriate tools (pylint, flake8, black, etc.)
  2. Run checks: Execute linters on code
  3. Review issues: Analyze warnings and errors
  4. Fix problems: Address high-priority issues
  5. Verify fixes: Re-run linters to confirm

Output Format

Lint report:

  • File path and line number
  • Issue type (style, convention, error, warning)
  • Issue description
  • Suggested fix or reference
  • Severity level

References

  • See CLAUDE.md > Pre-commit Hooks for automated checking
  • See 
    quality-run-linters
    skill for comprehensive linting
  • See quality standards in CLAUDE.md for project guidelines