agentleFS
Sign inStart free
docxologydocxology/template/.github/actions/check-browser/AGENTS.md

template / check-browser

AGENTS.md20 starsChanged 13 days agoApache-2.0View on GitHub

Selects the installed Google Chrome runtime for native consumer controls. See README.md for the assertions and callers. - The checks are blocking: file present, executable, not a symlink, resources.pak present, --version succeeds. Removing any one of them lets a Chromium development snapshot stand in for the supported runtime. - The action exports CHROMEEXECUTABLEPATH into $GITHUB_ENV; consumers read that exact name. Do not rename it or print a user-controlled path. - Callers keep their own if: (matrix.browser, or unconditional in the…

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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. Very specific:

    Run actionlint after edits, keep README.md accurate, and confirm both ci.yml callers still gate on their original condition.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

check-browser — agent notes

Selects the installed Google Chrome runtime for native consumer controls. See README.md for the assertions and callers.

Contract

  • The checks are blocking: file present, executable, not a symlink, resources.pak present, --version succeeds. Removing any one of them lets a Chromium development snapshot stand in for the supported runtime.
  • The action exports CHROME_EXECUTABLE_PATH into $GITHUB_ENV; consumers read that exact name. Do not rename it or print a user-controlled path.
  • Callers keep their own if: (matrix.browser, or unconditional in the test-infra prep). This action decides nothing about selection.
  • setup-acceptance-documents intentionally keeps a separate Linux check: it fails with a preparation-specific message and runs inside the native branch that also prepares TeX. Do not merge the two without preserving that message.

Editing

  • Run actionlint after edits, keep README.md accurate, and confirm both ci.yml callers still gate on their original condition.

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.

Reviews can't be read right now.

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