Repository navigation
Expand file tree
/
Copy pathcommunique.toml
More file actions
24 lines (20 loc) 路 1.62 KB
/
Copy pathcommunique.toml
File metadata and controls
24 lines (20 loc) 路 1.62 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
context = """
claudecode.nvim is a Neovim plugin written in pure Lua with zero dependencies. It implements the same WebSocket-based MCP protocol as Anthropic's official IDE extensions, letting the Claude CLI drive Neovim: opening files, reading selections and diagnostics, showing native diffs, and managing terminal sessions.
Releases matter to Neovim users who install the plugin via their package manager and to integrators relying on MCP tool behavior. Call out changes to the public setup() configuration (such as terminal or diff_opts), MCP tool behavior and compatibility with the VS Code extension, supported Neovim versions, file explorer and terminal integrations (snacks.nvim, native, external, nvim-tree, oil.nvim, neo-tree, mini.files), and any breaking changes to keybindings or commands.
Primary readers are Neovim users and plugin integrators, not the plugin's own maintainers, so frame notes around user-visible impact rather than internal refactors.
"""
system_extra = """
Write direct, practical release notes for Neovim users and integrators.
Lead with what changed and why it matters.
Use plain Markdown with no emoji.
Group changes into clear sections (for example Features, Fixes, Breaking Changes) and keep them concise.
Avoid marketing language.
Provide concrete migration guidance when configuration options, commands, or MCP tool behavior changed.
Do not mention version-only release preparation commits unless they affect users.
Do not invent changes that are not supported by the commits, pull requests, or diffs.
"""
[defaults]
model = "claude-opus-4-8"
repo = "coder/claudecode.nvim"
verify_links = true
match_style = true