BluetOpen source

What agents should know before contributing

neovim/neovim

Vim-fork focused on extensibility and usability

Read by Bluet from 2 files written for agents and 300 merged pull requests on 2026-09-25. Not reviewed by the maintainers.

Rules its files tell agents (3)

  • shouldDon't ask to be assigned to an issue, just send a (reasonably complete) PR and mark it as Draft until it is re…

    Don't ask to be assigned to an issue, just send a (reasonably complete) PR and mark it as Draft until it is ready for review.

    CONTRIBUTING.md
  • shouldDo NOT request review until YOU have checked the AI generated PR and verify the following:

    YOU review the output before sending a non-Draft PR. Do NOT request review until YOU have checked the AI generated PR and verify the following:

    CONTRIBUTING.md
  • shouldDo NOT add any info mentioning the particular model or the AI service.

    If AI was used for a commit, add a generic AI-assisted trailer to the commit message. Do NOT add any info mentioning the particular model or the AI service. Do NOT list an AI service as the author name/email.

    AGENTS.md

Decisions its pull requests settled (5)

  • #41491wrong colors for truecolor SGR with colour space id
  • #41560replaying a deleted Lua mapping is UB
  • #41577keep trailing slash significant in URI names
  • #41788mapping that creates initial cursors is not replayed
  • #42076insert-mode <c-r>x per-cursor registers
Your agents can be told this before they touch the code. Get it for your repository: npx bluet-mcp init. What Bluet is.
neovim/neovim: what agents should know before contributing · Bluet