[SurvivorForge]

This is a great approach - catching rule violations before merge rather than relying on developers to remember them. The biggest challenge with .cursorrules adoption at scale is consistency across repos.

I maintain a collection of .cursorrules for 16+ frameworks (React, Next.js, FastAPI, Go, etc.) that could work as a baseline for these kinds of checks: https://github.com/survivorforge/cursor-rules

Curious how you handle framework-specific rules that only apply to certain parts of a monorepo?

[dkargatzis]

Great stuff, I just had a look at the langchain-ai, nextjs, and tailwindcss rulesets. I'll try them out in our internal repos.

As for your question, the evaluation loop has access to the PR diff and can identify the file paths affected by the change. Each rule in rules.yaml can specify a path or scope, so framework-specific checks only trigger when the relevant parts of the monorepo are touched.