agentleFS
Sign inStart free
TransformerLensOrgTransformerLensOrg/TransformerLens/.github/copilot-instructions.md

TransformerLens

Copilot instructions4k starsChanged 38 days agoMITView on GitHub

Read AGENTS.md at the repo root for the full set of project conventions, quickstart commands, repo layout, and hard rules — start with its TL;DR section. This file inlines the highest-friction defaults Copilot most often gets wrong. The full set of hard rules (numerics, parallel benchmarks, plan-file references, etc.) lives in AGENTS.md §10.

We split this copilot-instructions.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Don't add # type: ignore. Prefer isinstance / typing.cast.

    line 23
  2. Distinctive:

    Don't dismiss failing tests as "pre-existing" — investigate every failure.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
copilot-instructions.md

GitHub Copilot Instructions

Read AGENTS.md at the repo root for the full set of project conventions, quickstart commands, repo layout, and hard rules — start with its TL;DR section. This file inlines the highest-friction defaults Copilot most often gets wrong.

Top rules to remember

  1. Use uv, not pip or poetry. uv sync to install; uv run <cmd> or a make target to run anything.
  2. The Hooked* model classes were removed in 4.0; TransformerBridge is the one model system. transformer_lens/supported_models.py is the frozen legacy name/alias ledger; Bridge models live under transformer_lens/tools/model_registry/.
  3. Base PRs against dev, not main. PRs to main are maintainer-only.

Common commands

uv sync                  # install
make unit-test           # fast tests
make format              # pycln + isort + black
uv run mypy .            # type check
uv run docs-hot-reload   # live docs preview

Copilot-specific anti-patterns

  • Don't add # type: ignore. Prefer isinstance / typing.cast.
  • Don't dismiss failing tests as "pre-existing" — investigate every failure.

The full set of hard rules (numerics, parallel benchmarks, plan-file references, etc.) lives in AGENTS.md §10.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 3 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 3 mentionsOct 2026: 3 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the TransformerLensOrg/TransformerLens repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about TransformerLensOrg/TransformerLens

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

See all 25

Talked about on GitHub (25 times).

On GitHub · 25

20 more on GitHub
  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 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 repository4 other files it gives its agents.

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