streamshub-mcp / rules
streamshub/streamshub-mcp/.cursor/rules/code-review.mdc
Code review checklist for StreamsHub MCP pull requests
The rules real projects give Cursor's agent, from .cursor/rules.
streamshub/streamshub-mcp/.cursor/rules/code-review.mdc
Code review checklist for StreamsHub MCP pull requests
huggingface/nanotron/.cursor/rules/philosophy.mdc
Core development principles and workflow for the Nanotron project. Apply when discussing project architecture, planning new features, or reviewing code structure.
Small-snake/android-code-review-skills/.cursor/rules/android-code-review-skills.mdc
Review local Android diffs with android-code-review-skills.
chimera-defi/eth2-quickstart/.cursor/rules/code-review.mdc
Mandatory multi-pass code review before completing any task
golid-ai/golid/.cursor/rules/audit-bugs.mdc
Bug audit checklist — use when asked to review code for bugs, security issues, or quality problems
LightbridgeLab/CodeCannon/.cursor/rules/review.mdc
Code Cannon: Run a standalone code review on a pull request
Tencent/LoopForge/.cursor/rules/sql-standard.mdc
SQL 开发规范:索引规范、慢SQL防护、查询优化、分页规范、事务控制。由 developer / code-reviewer 按需加载。
aborroy/aiup-alfresco/.cursor/rules/aiup-alfresco.mdc
AIUP Alfresco extension conventions — read AGENTS.md and command specs before generating or reviewing code
Seriora-Research/seri-agent/.cursor/rules/code-quality.mdc
Code-quality rules (Karpathy guidelines) for writing, editing, or reviewing code.
neomatrix369/tripwire/.cursor/rules/code-review-graph.mdc
Prefer code-review-graph MCP tools before Grep/Glob/Read when exploring or reviewing this codebase
KangaKode/universal-agent-bootstrap/.cursor/rules/code-reviewer.mdc
Code review quality gate — enforces architecture, code quality, and security conventions. Use proactively after any code change.
danielvm-git/bigpowers/.cursor/rules/respond-review.mdc
Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.
galyarderlabs/galyarder-framework/.cursor/rules/code-review-expert.mdc
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
sordi-ai/skill-everything/.cursor/rules/review-deployment.mdc
Apply when reviewing code or planning a deployment. Pre-merge checks, migration ordering, rollback strategy, post-deploy verification.
galyarderlabs/galyarder-framework/.cursor/rules/adversarial-reviewer.mdc
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
nathanjohnpayne/mergepath/.cursor/rules/code-review.mdc
Code review policy — all AI-generated PRs must include self-review and flag external review triggers
galyarderlabs/galyarder-framework/.cursor/rules/receiving-code-review.mdc
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
eliranpv11/code-discipline-skills/.cursor/rules/code-discipline.mdc
Coding methodology for production-grade software development. Enforces structured thinking before coding, verifying reality, simplicity, surgical changes, contract awareness, and verifiable success criteria. Use when writing, reviewing, or refactoring any code that must remain correct and maintainable past initial delivery. Triggers include "fix a bug", "add a feature", "refactor", "review code", "clean up", or explicit "apply code-discipline". Do NOT use for throwaway scripts, one-off prototypes, or quick demos.
jefrnc/quant-llm-skills/.cursor/rules/code-review-for-quant.mdc
Use when reviewing or writing Python/Go/SQL code for quant research, backtests, market-data pipelines, or trading systems. Provides a structured checklist of failure modes specific to time-series financial code (lookahead, splits, snapshots, currency, NaN propagation, joint-filer dedup) that generic code review skips.
JustineDevs/Collection/.cursor/rules/production.mdc
The standard way for production teams to connect frontend and backend branches and ensure integration before merging to main is to use temporary integration or "test" branches for local verification, automated testing, and code review.
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Open a rule to see its discussion. Reports from people and their agents are coming.