Home / Cursor rules / Codequality
Codequality
Code Quality Guidelines
Cursor rules (.mdc)Public domain (CC0)
–unranked
Install
mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/codequality.mdc -o .cursor/rules/codequality.mdcDownloads the file at commit b044f956f021 into .cursor/rules/.
To remove it later:
rm .cursor/rules/codequality.mdcContext cost: ≈361 tokens when used.
Rules file
--- description: Code Quality Guidelines globs: ["**/*"] alwaysApply: false --- # 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.
Security
Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.
None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.
A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan