SkillHub ClubShip Full StackFull Stack

lint-code

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

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C3.9

Composite score

3.9

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install mvillmow-projectodyssey-lint-code

Repository

mvillmow/ProjectOdyssey

Skill path: .claude/skills/tier-1/lint-code

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

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: mvillmow.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install lint-code into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/mvillmow/ProjectOdyssey before adding lint-code to shared team environments
Use lint-code for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: lint-code
description: "Check code for style and quality issues. Use when validating code before commits."
mcp_fallback: none
category: analysis
tier: 1
---

# 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

```bash
# 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