agentleFS
Sign inStart free
vikas8520-codervikas8520-coder/nerve/.github/copilot-instructions.md

nerve

Copilot instructions0 starsChanged 3 months agoMITView on GitHub

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:

    Treat npm run test:coverage as a required gate for PR work.

    line 3
  2. Very specific:

    If a PR changes production code in src/, open-sse/, electron/, or bin/, it must include automated tests in the same PR.

    line 5
  3. Very specific:

    When reviewing or updating a PR, if the report shows missing tests or coverage below 60%, do not stop after reporting the problem.

    line 6
  4. Distinctive:

    Prefer the smallest test layer that proves the behavior:

    line 7

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

Nerve PR and Coverage Instructions

  • Treat npm run test:coverage as a required gate for PR work.
  • The repository minimum is 60% for statements, lines, functions, and branches.
  • If a PR changes production code in src/, open-sse/, electron/, or bin/, it must include automated tests in the same PR.
  • When reviewing or updating a PR, if the report shows missing tests or coverage below 60%, do not stop after reporting the problem. Add or update tests in the PR first, rerun the coverage gate, and only then ask for confirmation.
  • Prefer the smallest test layer that proves the behavior:
    • unit tests first
    • integration tests when multiple modules or DB state are involved
    • e2e only when the behavior is truly UI or workflow-dependent
  • For bug issues, try to encode the reproduction as an automated test before or alongside the fix.
  • In the final PR report, include:
    • the commands you ran
    • the changed test files
    • the final coverage result

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