add

name	add
description	Categorize new Neovim plugins and insert them into the correct markdown category files
metadata	{"short-description":"Add Neovim plugins to categorized markdown lists"}

Update each repo's plugin in the right markdown section, then create .reason.md summarizing why each category was chosen.

Tasks

1. Get a list of new plugins to add. Run cat .new_plugins.txt.
2. Read references/PLACEMENT_RULES.md and apply any matching placement rules.
3. Examine each plugin and their assigned categories. 3.1. Visit the corresponding repository on GitHub. 3.2. If any of the following items apply, remove the added plugins from the list. In the .reason.md table, set the Category column to - and write the exclusion reason in the Reason column.
   • The plugin is a fork of another repository.
   • It is a new colorscheme plugin.
   • The repository is not a Neovim plugin: standalone CLI/GUI tools, terminal apps, or libraries whose primary use is outside Neovim, even if the README mentions Neovim support or integration.
   • The plugin is written primarily in Vim script, or supports both Vim and Neovim (dual-compatible). This list is for Neovim-specific plugins only. Check the repository language stats and README statements such as "works with Vim 8/9".
   • The repository has no README.
   • The README is written in a language other than English.
   • The repository is a Neovim configuration rather than a plugin.
   • The repository is a sample plugin created solely for learning purposes.
4. For each plugin, confirm and update if the category is appropriate. 4.1. From the README or other files, the repository belongs to. 4.2. Prefer the plugin's domain or user workflow over implementation surface such as picker UI, completion source, or integration library. 4.3. In , consult the table of contents and locate the markdown file that contains that category. 4.4. Open that markdown file and insert the added plugin at the appropriate position.