agentleFS
Sign inStart free
zephyrproject-rtoszephyrproject-rtos/zephyr/.github/copilot-instructions.md

zephyr

Copilot instructions17k starsChanged 6 months agoApache-2.0View on GitHub

The instructions for AI coding agents working on this repository are in AGENTS.md at the repository root. Copilot cloud agent, Copilot code review and the IDE agents load that file directly; this file only covers the Copilot features that do not, and code review. - Follow AGENTS.md, doc/contribute/guidelines.rst and doc/contribute/style/. - Never add Signed-off-by: or Co-authored-by:; add one Assisted-by: Copilot:<model> trailer to commits you help write. - Report only concrete, verifiable problems: a rule violation with the rule, a bug…

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

5 rules. About 0 are common, 1 is distinctive, and 4 are 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow AGENTS.md, doc/contribute/guidelines.rst and doc/contribute/style/.

    line 14
  2. Very specific:

    Never add Signed-off-by: or Co-authored-by:.

    line 15
  3. Very specific:

    Do not request changes for anything CI catches (checkpatch, gitlint, compliance).

    line 22
  4. Distinctive:

    Do not flag style in lines the PR does not touch, and do not ask for tree-wide cleanups.

    line 24
  5. Very specific:

    Check commit messages: area: prefix, non-empty body, Signed-off-by present, exactly one Assisted-by: trailer when AI tools were used, no …

    line 25

≈ “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
<!-- SPDX-FileCopyrightText: Copyright The Zephyr Project Contributors SPDX-License-Identifier: Apache-2.0 -->

Zephyr Project — Copilot Instructions

The instructions for AI coding agents working on this repository are in AGENTS.md at the repository root. Copilot cloud agent, Copilot code review and the IDE agents load that file directly; this file only covers the Copilot features that do not, and code review.

All Copilot features

  • Follow AGENTS.md, doc/contribute/guidelines.rst and doc/contribute/style/.
  • Never add Signed-off-by: or Co-authored-by:; add one Assisted-by: Copilot:<model> trailer to commits you help write.

Code review

  • Report only concrete, verifiable problems: a rule violation with the rule, a bug with the input that triggers it, a missing test with the untested behavior. Skip praise and summaries.
  • Do not request changes for anything CI catches (checkpatch, gitlint, compliance); reviewers are asked not to (doc/contribute/reviewer_expectations.rst).
  • Do not flag style in lines the PR does not touch, and do not ask for tree-wide cleanups.
  • Check commit messages: area: prefix, non-empty body, Signed-off-by present, exactly one Assisted-by: trailer when AI tools were used, no Co-authored-by. A change that addresses an issue carries Fixes #N in the PR description or a commit.

Download now (ZIP)

Trending

Quiet since September.about the whole repository

Dec 2025: 3 mentionsJan 2026: 3 mentionsFeb 2026: 3 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 3 mentionsAug 2026: 1 mentionSep 2026: 3 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the zephyrproject-rtos/zephyr repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about zephyrproject-rtos/zephyr

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

See all 72

Talked about on YouTube, GitHub, Stack Overflow, Hacker News and Bluesky (72 times).

On YouTube · 25

20 more on YouTube

On GitHub · 25

20 more on GitHub

On Stack Overflow · 19

14 more on Stack Overflow
  • 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 repository2 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