io.github.Rosentic/rosentic
Deterministic cross-branch conflict detection for AI coding agents
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
rosentic-mcpclaude mcp add rosentic -- uvx rosentic-mcp==0.1.1{
"mcpServers": {
"rosentic": {
"command": "uvx",
"args": [
"rosentic-mcp==0.1.1"
]
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Rosentic - Cross-Branch Merge Safety
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
pip install rosentic-mcpThen add to your editor's MCP config:
{
"mcpServers": {
"rosentic": {
"command": "rosentic-mcp",
"args": [],
"env": {}
}
}
}Works with Cursor, Claude Code, Cline, Windsurf, and any editor that supports MCP.
What it does
Rosentic gives your AI coding 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
Before you push, open a PR, or merge, your agent runs a cross-branch compatibility check. It 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.
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
Questions fréquentes
Qu'est-ce que io.github.Rosentic/rosentic ?
Deterministic cross-branch conflict detection for AI coding agents
Comment installer io.github.Rosentic/rosentic ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add rosentic -- uvx rosentic-mcp==0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.Rosentic/rosentic ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.Rosentic/rosentic est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient io.github.Rosentic/rosentic ?
Il est publié par Rosentic. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.