codequality
via PatrickJS/awesome-cursorrules
Enforce disciplined code review practices and focused AI assistance behavior.
What is codequality?
This rule establishes behavioral guidelines for code review and AI-assisted development, emphasizing verification, efficiency, and respect for existing code. Use it to maintain consistent, professional interactions during code changes and to prevent common AI assistant anti-patterns like over-apologizing, unnecessary summaries, or speculative changes.
- Require verification of information before presentation to avoid assumptions
- Enforce file-by-file changes with review opportunities to catch mistakes
- Eliminate apologies and understanding-feedback comments from responses
- Prevent whitespace-only suggestions and unnecessary change summaries
- Preserve existing code structures and avoid inventing unrequested modifications
- Consolidate edits into single chunks per file rather than multi-step instructions
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
Code Quality Guidelines
Verify Information
Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
File-by-File Changes
Make changes file by file and give me a chance to spot mistakes.
No Apologies
Never use apologies.
No Understanding Feedback
Avoid giving feedback about understanding in comments or documentation.
No Whitespace Suggestions
Don't suggest whitespace changes.
No Summaries
Don't summarize changes made.
No Inventions
Don't invent changes other than what's explicitly requested.
No Unnecessary Confirmations
Don't ask for confirmation of information already provided in the context.
Preserve Existing Code
Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.
Single Chunk Edits
Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
No Implementation Checks
Don't ask the user to verify implementations that are visible in the provided context.
No Unnecessary Updates
Don't suggest updates or changes to files when there are no actual modifications needed.
Provide Real File Links
Always provide links to the real files, not x.md.
No Current Implementation
Don't show or discuss the current implementation unless specifically requested.
Related rules
Best practices and syntax guidelines for Convex backend development.
Modern C++ and CMake with RAII, const-correctness, and safe error handling.
C++ development guidelines covering naming, functions, classes, memory management, and project structure.
Expert React + TypeScript + shadcn/ui development guidance with modern tooling best practices.
7 production-tested rules for dependency discipline, error handling, state management, webhook security, and database safety.
Next.js 14 + Tailwind CSS + TypeScript setup guide with SEO optimization and App Router best practices.