commit.lint

Format and lint Python code with ruff after tests pass.

49|3|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/Unsupervisedcom/deepwork --skill commit-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit.lint
Source: https://github.com/Unsupervisedcom/deepwork/tree/main/.claude/skills/commit.lint
Command: npx skills add https://github.com/Unsupervisedcom/deepwork --skill commit-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill formats and lints code with ruff using a sub-agent. It ensures code style compliance after tests pass to maintain a clean codebase.

Core Features & Use Cases

  • Automated Formatting: Apply ruff format to standardize code style across the project.
  • Automated Linting with Fixes: Use ruff check --fix to automatically correct issues where possible.
  • Verification: Run a final ruff check to guarantee there are no remaining issues.
  • Isolation via Sub-Agent: Leverage a sub-agent to keep main conversation context lean during lint tasks.
  • Use Case: Integrate into your commit workflow so Python projects pass style checks before merging.

Quick Start

To start, trigger the commit.lint step after your test suite completes. The sub-agent will perform the linting and formatting steps as described below:

  • Run ruff format .
  • Run ruff check --fix .
  • Run ruff check . to verify there are no remaining issues.

Frequently Asked Questions about commit.lint

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

FAQPage Schema
How do I format and lint Python code with ruff automatically before a commit?

Automated Python code formatting with ruff executes via a sub-agent to keep the main context lean. It runs ruff format, applies ruff check --fix, and verifies no remaining issues before merging.

How does a sub-agent handle code linting and formatting tasks?

A sub-agent handles code linting and formatting by executing ruff commands independently, which keeps the main conversation context lean. It sequentially applies formatting, auto-fixes issues, and verifies the final state.

What is the best way to ensure Python code style compliance after tests pass?

The best way to ensure Python code style compliance after tests pass is running ruff format and ruff check --fix in a sub-agent. This automated workflow standardizes code style and corrects issues before committing.

Does this automated ruff check workflow apply to any Python project?

Yes, this automated ruff check workflow applies to Python projects that run tests and require automated style checks. It integrates directly into the commit workflow to maintain a clean codebase.

What steps does ruff check --fix perform during the commit workflow?

During the commit workflow, ruff check --fix automatically corrects linting issues where possible after formatting. A final ruff check then runs to verify there are no remaining issues before the code is committed.