agentleFS
DINAKAR-SDINAKAR-S/company-ai-os/.claude/skills/lint/SKILL.md

lint

Skill2 starsChanged 3 months agoMITView on GitHub

Run the LINT operation — health-check the vault for contradictions, stale notes, orphans, dead paths, and gaps. Use when the user says "lint", "health check", "check the vault", or "/lint".

82 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 18 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 27 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 5 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

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

The file

Files
SKILL.md

Lint the Vault

Scan all of entities/, index.md, and entities/Routing.md for:

  1. Contradictions — two notes stating conflicting facts.
  2. Stale notes — updated: older than ~90 days AND the real folder/system has visibly changed (check path: contents if local).
  3. Orphans — notes with no [[links]] in or out.
  4. Dead paths — path: pointing to a folder that doesn't exist.
  5. Gaps — entities mentioned as [[links]] or in Routing rows with no note file.
  6. Index drift — notes missing from index.md, or index entries with no file.
  7. Routing drift — entity with a path: but no Routing row, or vice versa.

Report as a table: # | type | where | issue | suggested fix. Fix only with confirmation. Then log: ## [date] lint | N issues → M fixed

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.