agentleFS
Sign inStart free
GitHubKnown publishergithub/plugin-marketplace-starter/.github/copilot-instructions.md

plugin-marketplace-starter

Copilot instructions1 starsChanged 22 days agoMITView on GitHub

This repository is a marketplace of Copilot plugins. Before changing anything, read AGENTS.md for the maintenance rules and CONTRIBUTING.md for the change checklist. - Keep each plugin self-contained, and change its manifest, catalog entry, changelog, .vally.yaml entries, and evals together. Use npm run new-plugin, npm run remove-plugin (or remove-example), and npm run rename-marketplace instead of editing registrations by hand. - Run npm run build after changing generated-file sources, then npm run verify. - Don't run npm run eval, npm run…

The file

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

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    Keep each plugin self-contained, and change its manifest, catalog entry, changelog, .vally.yaml entries, and evals together.

    line 7
  2. Very specific:

    Run npm run build after changing generated-file sources, then npm run verify.

    line 11
  3. Very specific:

    Don't run npm run eval, npm run eval:smoke, or the evals workflow unless asked.

    line 12

≈ “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

Copilot instructions

This repository is a marketplace of Copilot plugins. Before changing anything, read AGENTS.md for the maintenance rules and CONTRIBUTING.md for the change checklist.

  • Keep each plugin self-contained, and change its manifest, catalog entry, changelog, .vally.yaml entries, and evals together. Use npm run new-plugin, npm run remove-plugin (or remove-example), and npm run rename-marketplace instead of editing registrations by hand.
  • Run npm run build after changing generated-file sources, then npm run verify.
  • Don't run npm run eval, npm run eval:smoke, or the evals workflow unless asked; they spend AI credits. npm run eval:list and npm run check-remotes don't call a model.

This file applies to work in this repository only. Installing a plugin from the marketplace doesn't copy it into other projects.

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