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
- microsoft/coreai-design-systemtheir own version, first seen Nov 15, 2026
- jakubtobiasz/second-brain-templatetheir own version, first seen Nov 15, 2026
- wikilayer/skillstheir own version, first seen Nov 13, 2026
- playingpossumm/loose-endstheir own version, first seen Nov 10, 2026
- HurricaHjz/second-yourselftheir own version, first seen Nov 9, 2026
- PMDevSolutions/Flaviantheir own version, first seen Nov 8, 2026
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.
ArtemXTechSkillquery
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
JaimeGBASkillingest
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
BugRogerSkillproject
Project lifecycle management. Dispatches to Ada.
Also in 5 projects that use this
PydanticSkillcoverage
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
seongjaeryuSkillsave
Complete and save your current thinking to Bindly
Also in 5 projects that use this
GitHubSkillstate-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
Other versions82 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 82
- ray-project/ray★ 44ksame name
- FalkorDB/FalkorDB★ 11ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- aaddrick/claude-desktop-debian★ 5.5ksame name
- cloudposse/atmos★ 1.4ksame name
- ethereum/execution-specs★ 1.2ksame name
- adobe/S3Mock★ 1.2ksame name
- maxGraph/maxGraph★ 1.2ksame name
- jason-effi-lab/karpathy-llm-wiki-vault★ 718same name
72 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-evaluationSkill
- algorithm-developmentSkill
- buildSkill
- change-reviewSkill
- container-buildSkill
- engineering-solution-designSkill
- interface-migrationSkill
- issue-localizationSkill
- long-horizon-developmentSkill
- model-artifact-integrationSkill
- multi-repo-devSkill
- performance-optimizationSkill
- repository-agent-setupSkill
- simulation-regressionSkill
- test-impact-analysisSkill
- unified-core-runtimeSkill
- vendorSkill
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
- Distinctive: line 10
Use this when checking source formatting or lint before submitting changes.
- Distinctive: line 25
Run all repository lint and formatting checks with:
- Distinctive: line 64
Stop and report the first actionable error.
- Distinctive: line 67
Do not run Apollo lint or Bazel outside the managed container.
- Distinctive: line 68
Do not run Bazel as root or bypass the shared repository and disk caches.
- Very specific: line 69
Do not use apollo.sh clean to address lint failures.
“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.
Files
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 enterenterdefaults todevand starts it if needed. Run lint from/apolloas the mapped non-root user.
Steps
Run all repository lint and formatting checks with:
./apollo.sh lint --all./apollo.sh lintwithout a check selector is invalid; the underlying script requires--allor 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 toHEAD, not uncommitted working-tree changes. Use--allto 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.ccUsing 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 cleanto address lint failures.
Sources (SSOT)
apollo.shscripts/ci/apollo_lint.shdocker/scripts/whl.sh
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
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.

