Rosentic
Rosentic - Cross-Branch Merge Safety for Cursor
Rosentic checks whether your active branches are compatible with each other before merge. It detects broken function signatures, HTTP route conflicts, and schema mismatches across 15+ languages using deterministic AST analysis.
This is not AI code review. Rosentic finds structural contract conflicts that would cause runtime failures after merge - the kind of breaks that tests don't catch because they only run on one branch at a time.
Install
In Cursor, run:
/add-plugin rosentic
Or search "Rosentic" in the Plugin Marketplace (Cmd+Shift+J > Plugins).
Prerequisite
The plugin requires the rosentic-mcp command:
pip install rosentic-mcp
What it does
Rosentic gives your Cursor agent three MCP tools:
| Tool | Purpose |
|---|---|
check_conflicts | Scan a repo for cross-branch contract conflicts |
explain_conflict | Explain a specific finding and what to do about it |
list_branches | List active branches so the agent can choose what to scan |
Example conflicts Rosentic catches
- Branch A adds a required parameter to
createOrder(). Branch B callscreateOrder()with the old signature. Both pass CI. Merge breaks production. - Branch A changes
POST /api/usersto requireemailin the request body. Branch B's frontend still sends the old payload. - Branch A removes a field from a GraphQL type that Branch B's query depends on.
How it works
When you're about to push, open a PR, or merge, the plugin's skill prompts Cursor's agent to run a cross-branch compatibility check. The agent calls check_conflicts, which scans your repo's branch heads using tree-sitter AST parsing and reports any conflicts.
No code leaves your machine. The scan runs locally against your git repo.
What this plugin includes
- MCP server config (
mcp.json) - connects Cursor to therosentic-mcpcommand - Skill (
skills/cross-branch-check/) - teaches the agent when and how to run merge safety checks - Rule (
rules/merge-safety.mdc) - surfaces merge safety at push/PR boundaries
Compared to Semgrep Guardian
Semgrep Guardian checks each file for security vulnerabilities and code issues. Rosentic checks whether your branches are compatible with each other. They solve different problems and work well together:
- Semgrep Guardian: "Is this code safe and correct on its own?"
- Rosentic: "Will this branch break other branches when merged?"
Links
Server Config
{
"mcpServers": {
"rosentic": {
"command": "rosentic-mcp",
"args": [],
"env": {}
}
}
}