lint-code

Lint Python and Mojo files with pylint, flake8, Black, and Mojo formatting.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ProjectOdyssey --skill lint-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-code
Source: https://github.com/mvillmow/ProjectOdyssey/tree/main/.claude/skills/tier-1/lint-code
Command: npx skills add https://github.com/mvillmow/ProjectOdyssey --skill lint-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pylint, flake8, black, mojo, pixi.

What problem does it solve?

Manual code review for style and quality issues is time-consuming and error-prone, leading to inconsistent codebases and potential bugs. This skill automates that process.

Core Features & Use Cases

  • Comprehensive Linting: Runs various tools (pylint, flake8, black, mojo format) to identify style violations, potential bugs, and code quality problems.
  • Pre-commit Validation: Integrates seamlessly into your pre-commit workflow to ensure code quality before changes are committed.
  • Use Case: Before pushing your feature branch, use this skill to automatically lint all your Mojo and Python files, ensuring they meet project standards and preventing CI failures.

Quick Start

Use the lint-code skill to check the formatting and style of your current Mojo and Python files.

Frequently Asked Questions about lint-code

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

FAQPage Schema
How do I automatically check code quality before committing changes?

Pre-commit validation automatically lints your code before commits. This skill integrates pylint, flake8, Black, and Mojo formatting to catch style violations and potential bugs, preventing CI failures and ensuring your changes meet project standards before they're pushed.

What linting tools does this skill use for Python and Mojo files?

This skill runs pylint, flake8, Black, and Mojo format as a consolidated lint plan via pixi. These tools identify style violations, unused variables, typos, and enforce code consistency across your Python and Mojo source files.

Can I use this skill to enforce consistent code style across my project?

Yes. The skill enforces style consistency by running multiple linters—Black for formatting, pylint and flake8 for code quality—ensuring all team members follow the same standards and catching deviations automatically.

How does linting help catch bugs before code review?

Linting identifies simple mistakes like unused variables and typos automatically, reducing manual review overhead. By catching these issues early in the pre-commit stage, you prevent buggy code from reaching CI pipelines or slowing down code reviews.

Do I need to install and configure each linter separately?

No. This skill consolidates pylint, flake8, Black, and Mojo formatting into a single lint plan via pixi, so you run all linters together without managing multiple tool configurations independently.