Recommend a plugin from the CLI

The best plugin recommendations often come from a teammate who just used one to solve a real problem, not from a policy handed down from above. Syntic Code supports this grassroots path: a developer who has found a plugin useful can recommend it to colleagues directly from syntic, turning individual discovery into shared adoption without anyone filing a ticket or waiting on an administrator.

When a developer recommends

This path fits the moment right after a plugin has proven its worth. A developer finishes a task with the help of a plugin, realizes their team would benefit, and wants to pass it along while the value is fresh. Because the recommendation comes from a peer and points at a specific, concrete win, it tends to land better than a generic announcement. It is the natural way for a good internal plugin to spread across a team by word of mouth.

Making a recommendation

From within the CLI, recommend a plugin by name so your teammates receive a pointer to it and can install it in one step:

syntic plugin recommend issue-linker \
  --note "cuts our PR-to-ticket linking from minutes to seconds"

The recommendation carries the plugin’s identity and your short note explaining why it helped, so the recipient understands the context before deciding to install.

How it complements central policy

CLI recommendations and organization-wide recommendations are two ends of the same spectrum, and they work best together. Grassroots recommendations surface which plugins developers actually value, giving administrators evidence about what to standardize on. A plugin that spreads widely through peer recommendation is a strong candidate to become an official organization recommendation. In this way the bottom-up path feeds the top-down one, and the catalog grows around tools that have already proven themselves in practice.