agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/nexamem/.github/copilot-instructions.md

nexamem

Copilot instructions1 starsChanged 16 days agoMITView 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,336 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.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Follow best practices for open-source Python packages (PEP 517/518, pyproject.toml, tests, docs, etc).

    line 4
  2. Distinctive:

    All code should be compatible with Python 3.11+.

    line 5
  3. Distinctive:

    Use pip, venv, and pip-tools for dependency management.

    line 6
  4. Distinctive:

    Use clear, concise docstrings and type hints.

    line 7
  5. Very specific:

    Write tests in the tests/ directory using pytest.

    line 8
  6. Distinctive:

    Run Pytest before committing changes to ensure all tests pass.

    line 9
  7. Very specific:

    Create a whl file for distribution when ready.

    line 11

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

Use this file to provide workspace-specific custom instructions to Copilot. For more details, visit https://code.visualstudio.com/docs/copilot/copilot-customization#_use-a-githubcopilotinstructionsmd-file

  • This is a Python package project for managing NexaMem chatbot history.
  • Follow best practices for open-source Python packages (PEP 517/518, pyproject.toml, tests, docs, etc).
  • All code should be compatible with Python 3.11+; CI targets Python 3.11, 3.12, and 3.13.
  • Use pip, venv, and pip-tools for dependency management; do not require uv.
  • Use clear, concise docstrings and type hints.
  • Write tests in the tests/ directory using pytest.
  • Run Pytest before committing changes to ensure all tests pass.
  • Require at least 90% overall unit-test line coverage across the complete package, including legacy modules. Keep Ruff and strict mypy checks blocking.
  • Create a whl file for distribution when ready.

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