agentleFS
wheeloswheelos/apollo-lite/.agents/skills/lint/SKILL.md

lint

Skill177 starsChanged 7 days agoApache-2.0View on GitHub

Apollo-Lite lint and formatting workflow. Use when checking Python, shell, C++, or Bazel formatting and lint in the managed dev container.

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

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when checking source formatting or lint before submitting changes.

    line 10
  2. Distinctive:

    Run all repository lint and formatting checks with:

    line 25
  3. Distinctive:

    Stop and report the first actionable error.

    line 64
  4. Distinctive:

    Do not run Apollo lint or Bazel outside the managed container.

    line 67
  5. Distinctive:

    Do not run Bazel as root or bypass the shared repository and disk caches.

    line 68
  6. Very specific:

    Do not use apollo.sh clean to address lint failures.

    line 69

“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lint and Formatting

When

Use this when checking source formatting or lint before submitting changes.

Prerequisites

  • From the repository root, enter the managed development container:

    bash docker/scripts/whl.sh enter
  • enter defaults to dev and starts it if needed. Run lint from /apollo as the mapped non-root user.

Steps

  • Run all repository lint and formatting checks with:

    ./apollo.sh lint --all

    ./apollo.sh lint without a check selector is invalid; the underlying script requires --all or one or more specific checks.

  • To narrow checks, pass supported selectors such as --py, --sh, --cpp-format, --cpp-lint, or --bazel. Use --diff <base> for CI-style checks against committed changes since a known base; this mode compares the base to HEAD, not uncommitted working-tree changes. Use --all to include local edits.
  • The full check covers Python formatting/lint (Black, isort, Flake8), shell lint (ShellCheck), C++ formatting (Clang-Format), standalone cpplint, and Bazel formatting (Buildifier).
  • C++ lint is an explicit review operation, never a compilation dependency. For a small uncommitted change, run standalone cpplint directly in the container, for example:

    cpplint --repository=pkgs/hardware/camera pkgs/hardware/camera/camera_component.cc

    Using the source directory keeps logical Bazel include prefixes from being mistaken for missing self-headers. Diagnose and fix reported issues rather than suppressing whole categories.

  • The wrapper invokes check-only modes. Review reported changes and make formatting edits only when they are within the requested scope.

Acceptance

  • Selected checks exit successfully and cover the changed file types.
  • For uncommitted edits, use working-tree checks rather than relying on --diff <base>.
  • A skipped check or missing tool is not a successful lint result.

Failure handling

  • Stop and report the first actionable error. Do not install packages, alter lint configuration, or retry with changed options without a validation reason and permission where scope expands.
  • Do not run Apollo lint or Bazel outside the managed container.
  • Do not run Bazel as root or bypass the shared repository and disk caches.
  • Do not use apollo.sh clean to address lint failures.

Sources (SSOT)

  • apollo.sh
  • scripts/ci/apollo_lint.sh
  • docker/scripts/whl.sh

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.