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

FixLab

Copilot instructions0 starsChanged 59 days agoMITView on GitHub

FixLab is a product-neutral Agency Copilot plugin and CLI for evidence-backed defect validation across React frontends and .NET backends. Consumer-specific product names and boundaries must remain outside the reusable product. Before editing, read AGENTS.md, the nearest module-level AGENTS.md, docs/architecture.md, and the affected tests. Preserve unrelated worktree changes. Prefer focused changes and existing helpers over new dependencies. Every implementation must preserve these invariants: - local listeners bind to 127.0.0.1; - only FixLab-owned processes and artifact directories may be removed; - credentials,…

  • 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,349 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 repository5 other files it gives its agents.

The file

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

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

  • 3

    Very specific

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

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

    Before editing, read AGENTS.md, the nearest module-level AGENTS.md, docs/architecture.md, and the affected tests.

    line 7
  2. Distinctive:

    Every implementation must preserve these invariants:

    line 11
  3. Very specific:

    only FixLab-owned processes and artifact directories may be removed.

    line 14
  4. Very specific:

    Use npm run validate as the repository-wide completion gate.

    line 21

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

FixLab is a product-neutral Agency Copilot plugin and CLI for evidence-backed defect validation across React frontends and .NET backends. Consumer-specific product names and boundaries must remain outside the reusable product.

Before editing, read AGENTS.md, the nearest module-level AGENTS.md, docs/architecture.md, and the affected tests. Preserve unrelated worktree changes. Prefer focused changes and existing helpers over new dependencies.

Every implementation must preserve these invariants:

  • local listeners bind to 127.0.0.1;
  • only FixLab-owned processes and artifact directories may be removed;
  • credentials, private data, browser state, and authorization headers never enter source, prompts, logs, responses, or durable caches;
  • required validation gates pass or are explicitly reported as blocked, failed, timed out, or skipped with risk;
  • repository-specific behavior remains in profiles, templates, or examples.

Use npm run validate as the repository-wide completion gate. Add focused node:test coverage for behavioral changes and update directly related documentation. Pull requests must use the repository template and identify validation evidence, skipped gates, and security or compatibility risks.

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