Rosentic
About
Deterministic cross-branch conflict detection for AI coding agents. Scans your git repo for function signature mismatches, HTTP route conflicts, and schema breaks across branches using tree-sitter AST analysis. Catches the merge failures that CI misses because tests only run on o
Details
- Author
- Rosentic
- Downloads
- 320
- Categories
- Developer Tools, AI
Jump to
- Cross-branch contract conflict detection before merge
- Catches broken function signatures and HTTP route conflicts
- Detects schema mismatches across 15+ languages
- Deterministic AST analysis (not AI code review)
- All scans run locally; no code leaves your machine
- Includes MCP tools, skill, and rule for Cursor agent
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
RosenticCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install the Rosentic plugin in Cursor by running /add-plugin rosentic or searching “Rosentic” in the Plugin Marketplace. Prerequisite: install the rosentic-mcp command via pip install rosentic-mcp. Once installed, the Cursor agent automatically uses three MCP tools—check_conflicts, explain_conflict, and list_branches—to run cross-branch compatibility checks at push, PR, or merge time.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"rosentic": {
"rosentic": {
"command": "rosentic-mcp",
"args": [],
"env": []
}
}
}
}McpServers
{
"rosentic": {
"command": "rosentic-mcp",
"args": [],
"env": []
}
}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:
`bash
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 calls createOrder() with the old signature. Both pass CI. Merge breaks production.
- Branch A changes POST /api/users to require email in 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 the rosentic-mcp command
- 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
- Rosentic website - GitHub Action - PyPI packageSign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
