sync c++ and generic instructions with upstream#359
sync c++ and generic instructions with upstream#359softhack007 wants to merge 2 commits intomdevfrom
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 50 minutes and 5 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughUpdates documentation for AI-assisted code review and C++ coding standards. Modifies AI-generated code attribution format, adds feature-flag name validation rules, expands const/constexpr guidance, updates bit-shift operation guidance for ESP8266, and introduces human-only instruction blocks. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
.github/copilot-instructions.md (1)
97-99: Add a HUMAN_ONLY reference example for the new feature-flag allowlist rule.The new AI-facing verification rule is good, but adding a short HUMAN_ONLY example (e.g., typo → corrected flag) would keep reference material aligned for contributors.
As per coding guidelines: “If new AI-facing rules were added without updating a related HUMAN_ONLY reference section, note this as a suggestion (not a required fix).”
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/copilot-instructions.md around lines 97 - 99, Add a HUMAN_ONLY reference example for the new AI-facing feature-flag allowlist rule by inserting a short example that shows a common typo and the corrected flag (e.g., "typo: WLED_IR_DISABLE → corrected: WLED_DISABLE_INFRARED") so human reviewers see how to map mistakes to the canonical names; reference the existing feature flag tokens (WLED_ENABLE_*, WLED_DISABLE_* and specific names like INFRARED, AOTA, MQTT) and place the example alongside the other HUMAN_ONLY examples for consistency with the new rule.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/cpp.instructions.md`:
- Around line 174-175: The sentence "Use `const &` (or `&`) inside loops - This
avoids constructing temporary objects on every access." has an extra space after
the closing backtick; remove the duplicate space so it reads "Use `const &` (or
`&`) inside loops - This avoids constructing temporary objects on every access."
to fix the spacing/wording issue.
- Around line 457-460: Update the heading "Bit Shifts Over Division (mainly for
RISC-V boards)" to reflect that ESP8266 is also affected—e.g., change it to "Bit
Shifts Over Division (RISC-V targets and ESP8266)" or "Bit Shifts Over Division
(RISC-V and ESP8266)"; ensure the new heading aligns with the paragraph text
that mentions ESP32/ESP32-S3 and RISC-V targets (ESP32-C3/C6/P4) and ESP8266 so
messaging is consistent.
---
Nitpick comments:
In @.github/copilot-instructions.md:
- Around line 97-99: Add a HUMAN_ONLY reference example for the new AI-facing
feature-flag allowlist rule by inserting a short example that shows a common
typo and the corrected flag (e.g., "typo: WLED_IR_DISABLE → corrected:
WLED_DISABLE_INFRARED") so human reviewers see how to map mistakes to the
canonical names; reference the existing feature flag tokens (WLED_ENABLE_*,
WLED_DISABLE_* and specific names like INFRARED, AOTA, MQTT) and place the
example alongside the other HUMAN_ONLY examples for consistency with the new
rule.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 87a2b556-9681-4ce3-aa4c-70851a64fcb3
📒 Files selected for processing (2)
.github/copilot-instructions.mddocs/cpp.instructions.md
|
@coderabbitai please check if |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: Length of output: 6099
Findings:
🧠 Learnings used |
updated instructions / coding guides, to incorporate changes from upstream WLED.
Summary by CodeRabbit