agentleFS
Sign inStart free
boxlite-aiboxlite-ai/boxlite/.github/AGENTS.md

boxlite

AGENTS.md2.6k starsChanged 34 days agoApache-2.0View on GitHub

Follow the root instructions. CI policy and implementation details live in the workflow guide. - Preserve documented check selection and quality/security gates unless the user requests a policy change. - Before expanding triggers or matrices, explain the missing coverage and check whether existing actions or builds can serve it. - Check existing runs for the current commit. No empty commits or draft/Ready toggles to force CI, or dispatches solely to warm caches. - Manual runs must serve the requested task.…

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 3 mentionsFeb 2026: 5 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 4 mentionsOct 2026: 31 mentionsNov 2026: 12 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the boxlite-ai/boxlite repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about boxlite-ai/boxlite

The biggest 5 of 56 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 56

Talked about on GitHub, Hacker News and Bluesky (56 times).

On GitHub · 50

45 more on GitHub
  • Other versions1 project uses a version of this.

    Word for word · 1

    1. boxlite-labs/boxlite★ 2.6k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository5 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the root instructions.

    line 3
  2. Distinctive:

    Before expanding triggers or matrices, explain the missing coverage and check whether existing actions or builds can serve it.

    line 10
  3. Distinctive:

    Check existing runs for the current commit.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “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
AGENTS.md

GitHub Actions

Follow the root instructions. CI policy and implementation details live in the workflow guide.

Changes

  • Preserve documented check selection and quality/security gates unless the user requests a policy change.
  • Before expanding triggers or matrices, explain the missing coverage and check whether existing actions or builds can serve it.

Runs

  • Check existing runs for the current commit. No empty commits or draft/Ready toggles to force CI, or dispatches solely to warm caches.
  • Manual runs must serve the requested task. Inspect the workflow, ref, inputs, and downstream side effects before dispatching.
  • Diagnose failures before retrying; target the affected job with gh run rerun --job JOB_ID. Diagnose again if it fails; no blind retry loops.

Verification

  • Workflow execution changes: run make test:apps:infra and applicable workflow linting locally. Markdown-only changes: check links and whitespace; no matrix dispatch.
  • Performance comparisons: report summed job runner time separately from elapsed time.

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