agentleFS
Sign inStart free
sovanticasovantica/engrava-mcp/.github/copilot-instructions.md

engrava-mcp

Copilot instructions1 starsChanged 52 days agoMITView on GitHub

Public repository (engrava-mcp) — Model Context Protocol server exposing Engrava as agent memory. License: MIT. Primary language: python 3.11+. Default to omitting the uncertain reference. Ask the maintainer in a PR comment or a draft message. The local commit-message hook gives you a fast feedback loop on commit-message hygiene; pay attention to its output.

The file

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

9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Use Conventional Commits 1.0.0: <type>(<scope>): <description>.

    line 10
  2. Very specific:

    Use only durable public identifiers: this repo's release tags (vX.Y.Z), this repo's GitHub issue/PR numbers (#N), and locally-documented …

    line 11
  3. Very specific:

    Default PR target: the active release/vX.Y.Z branch.

    line 13
  4. Distinctive:

    No internal identifiers, no abbreviations that wouldn't make sense to someone reading the repo for the first time.

    line 18
  5. Very specific:

    Follow the existing patterns in src/.

    line 22
  6. Very specific:

    Don't reference internal-looking identifiers or paths in commits, code comments, or PR descriptions.

    line 28
  7. Distinctive:

    Don't introduce dependencies without checking the project's existing stack — extra deps need explicit justification.

    line 29
  8. Very specific:

    Don't suggest --no-verify to skip the local commit-message hook except in maintainer-approved emergencies.

    line 30
  9. Distinctive:

    Default to omitting the uncertain reference.

    line 34

≈ “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
<!-- Generated by 0.1.0 (2026-09-01T21:02:53Z) from a shared template — do not edit directly. -->

Copilot Instructions — engrava-mcp

Public repository (engrava-mcp) — Model Context Protocol server exposing Engrava as agent memory.

License: MIT. Primary language: python 3.11+.

Commit messages

  • Use Conventional Commits 1.0.0: <type>(<scope>): <description>. See CLAUDE.md for the type table.
  • Use only durable public identifiers: this repo's release tags (vX.Y.Z), this repo's GitHub issue/PR numbers (#N), and locally-documented ADRs (docs/adr/ADR-NNN-*.md after the file exists here).
  • Generic feature descriptions are welcome; concise imperative subject lines preferred (max 72 chars).
  • Default PR target: the active release/vX.Y.Z branch. This repo has no dev branch; the version is set by hand in pyproject.toml and server.json, CHANGELOG.md is hand-maintained, and a release is a manual vX.Y.Z tag on main.

Branch names

  • Format: <type>/<kebab-description>. Plain English. ≤ 50 chars.
  • No internal identifiers, no abbreviations that wouldn't make sense to someone reading the repo for the first time.

Code style

  • Follow the existing patterns in src/. Read 3-5 nearby files before introducing a new pattern.
  • Adhere to the quality bar described in CLAUDE.md — linting clean, typing strict, coverage above threshold, no shortcuts.
  • Match the project's existing naming, file layout, and import conventions; don't invent new structures unprompted.

What to avoid

  • Don't reference internal-looking identifiers or paths in commits, code comments, or PR descriptions. If something feels like it belongs to a private workflow, leave it out and the maintainer can add a public mapping (a #N issue/PR reference) later.
  • Don't introduce dependencies without checking the project's existing stack — extra deps need explicit justification.
  • Don't suggest --no-verify to skip the local commit-message hook except in maintainer-approved emergencies.

When you're unsure

Default to omitting the uncertain reference. Ask the maintainer in a PR comment or a draft message. The local commit-message hook gives you a fast feedback loop on commit-message hygiene; pay attention to its output.

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