PluginBench
Rule

codequality

via PatrickJS/awesome-cursorrules

Enforce disciplined code review practices: verify facts, preserve code, avoid unnecessary commentary.

What is codequality?

This rule establishes operational guidelines for code review and modification workflows. It emphasizes verification of information, file-by-file changes with opportunity for feedback, and elimination of unnecessary commentary (apologies, summaries, confirmations). Use it to maintain focused, efficient code changes without speculative additions or whitespace-only modifications.

  • Require verification of information before presenting changes
  • Process changes file-by-file to catch mistakes early
  • Eliminate apologies, understanding feedback, and unnecessary confirmations from responses
  • Avoid whitespace-only suggestions and invented changes
  • Preserve existing code structures and unrelated functionalities
  • Provide edits in single chunks per file rather than step-by-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

Senior full-stack TypeScript, React, Node.js guidance with clean architecture, testing, and WHY-oriented reasoning.

**/*
41k
via PatrickJS/awesome-cursorrules

Quantitative factor research skills for designing, evaluating, and mining alpha factors in equities markets.

**/*
41k
via PatrickJS/awesome-cursorrules

Android development with Jetpack Compose, clean architecture, and Material Design 3.

**/*
41k
via PatrickJS/awesome-cursorrules

Angular development with Novo Elements UI library using standalone components.

**/*
41k
via PatrickJS/awesome-cursorrules

Expert Angular 18 + TypeScript development with Jest, emphasizing clean code and performance.

**/*
41k
via PatrickJS/awesome-cursorrules

Manage Kubernetes clusters, add-ons, stacks, and credentials via the Ankra CLI platform.

**/*.sh +5
41k
via PatrickJS/awesome-cursorrules