agentleFS
Sign inStart free
maya8237maya8237/MEOW/skills/lint/SKILL.md

lint

Skill3 starsChanged 34 days agoMITView on GitHub

Use when finding and fixing the project's configured lint findings in the current session, without a separate MEOW fixer agent.

80 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use query, ingest and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArtemXTechSkill

    query

    Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.

    Also in 17 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 26 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 4 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 5 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 4 projects that use this

  • AnthropicSkill

    digest

    Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

lint

Runs the project's [[lint]] commands and has you — this session — fix what they report, using meow native lint for the facts. Read ../_shared/native-mode.md for helper conventions. Never run plain meow run --lint-fix here: that spins up meow's own fixer agent, duplicating your work and racing your edits. Dependency or install problems: dependencies.

Native mode

  1. The project needs .meow/config.toml with at least one [[lint]] entry; otherwise tell the user and stop (point at the Integrations guide in meow ui or the online docs for the [[lint]] schema, or invoke /meow:onboard to configure it).
  2. Run meow native prepare --no-worktree --allow-dirty --work-dir "<project-path>" for max_rounds and docs_dir, then meow native round <docs_dir>/lint-fix.md --reset --work-dir "<project-path>".
  3. Auto-fix pass, then check: meow native lint --fix --all-blocking --work-dir "<project-path>". --all-blocking fixes every configured command unconditionally, matching meow run --lint-fix's own CLI behavior -- gate only controls what fails a review, not what this skill leaves alone.
    • "clean": true -> report that nothing is left and stop.
    • Otherwise call meow native round <docs_dir>/lint-fix.md --work-dir "<project-path>" before the first manual fix attempt; stop if exhausted. Each entry in blocking is a $ <command> block of raw linter output. Before editing, run meow native prompt lint-fixer --active-dir <active_dir> --work-dir "<project-path>" and follow its returned system_prompt, just as the CLI lint-fixer role follows lint_fixer_prompt. Fix each finding yourself with the smallest edit that resolves it, without unrelated refactoring; the skill's PostToolUse hook lints each edited file and reports leftovers; if your host ignores skill hooks, run meow native lint --file <path> --active-dir <active_dir> after each edit. Do not launch another agent.
  4. Re-check with meow native lint --all-blocking --work-dir "<project-path>"; call meow native round <docs_dir>/lint-fix.md --work-dir "<project-path>" before each further fix attempt and stop if it says exhausted.
  5. Report the final outcome: clean, or what is still outstanding and why (e.g. a project-wide type error needing a design decision).

CLI mode

Report-only, then fix by hand:

meow run --lint-fix --report-only --work-dir "<project-path>"

Exit 0 with Lint is clean -- no issues found. means done; otherwise fix each $ <command> block it printed and re-run to confirm.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free