← Browse

@ubie-oss/lint-and-fix

A

Automated linting and fixing loop using `make lint`. Use when you need to resolve linter violations across the codebase.

skillclaude

Install

agr install @ubie-oss/lint-and-fix --target claude

Writes 1 file into .claude/skills/, pinned to git-370dc846.

  • .claude/skills/lint-and-fix/SKILL.md

Document


name: lint-and-fix description: Automated linting and fixing loop using make lint. Use when you need to resolve linter violations across the codebase.

Lint and Fix

Purpose

This skill provides an autonomous loop to identify, fix, and verify linter violations in the codebase using the project's make lint command (which runs pre-commit).

Loop Logic

  1. Identify: Run make lint from the workspace root to list current violations.
  2. Analyze: Examine the linter output to understand which files and rules are failing.
  3. Fix: Apply targeted fixes for the identified violations.
    • Many linters in pre-commit (like black, ruff, prettier) can auto-fix issues.
    • If pre-commit auto-fixes files, review the changes.
    • If manual fixes are required, apply the minimum necessary change to resolve each error.
  4. Verify: Re-run make lint.
    • If all checks pass: Termination.
    • If new or remaining failures exist: Analyze the failure and repeat the loop.

Termination Criteria

  • make lint exits with code 0 (all checks passed).
  • Reached max iteration limit of 5 attempts.
  • No progress being made (same errors persisting despite fix attempts).

Examples

Scenario: Fixing formatting and imports

  1. make lint fails with ruff and black errors.
  2. Agent runs make lint again (some linters auto-fix).
  3. Agent reviews auto-fixed changes.
  4. make lint passes.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-370dc84690962026-07-31