Conversation
📝 WalkthroughWalkthroughThe pull request adds a new item to the Contents section of the README.md file, introducing a link for Ruleskill with accompanying descriptive text. The license line remains unchanged in substance. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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: 1
🤖 Fix all issues with AI agents
In `@README.md`:
- Around line 52-55: The Table of Contents contains an external link entry
"Ruleskill" which breaks the README rule that all TOC links must be relative and
must point to actual sections; either remove the "-
[Ruleskill](https://ruleskill.com) - We want to verify your code for the
RuleSkill Protocol. Claim your badge." line from the "Contents" list, or replace
it with a relative anchor that matches a new section heading you add (e.g., add
a "## Ruleskill" section) and place that TOC entry in the correct
alphabetical/category order; update the TOC entry text and anchor so it exactly
matches the new section heading to keep links accurate.
| ## Contents | ||
|
|
||
| - [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge. | ||
| - [Awesome Cursor Rules ](#awesome-cursor-rules-) |
There was a problem hiding this comment.
Fix TOC accuracy and relative-link requirement.
This entry points to an external URL and doesn’t correspond to a section in the README, which makes the table of contents inaccurate and violates the “all links are relative” rule. Either remove this item from Contents, or add a proper section with a relative anchor (and place it in the correct category/alphabetical order).
As per coding guidelines, Maintain the following structure in the README.md file... and Ensure all links in the README.md file are relative and correct.
🛠️ Suggested fix (remove from Contents)
- - [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## Contents | |
| - [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge. | |
| - [Awesome Cursor Rules ](#awesome-cursor-rules-) | |
| ## Contents | |
| - [Awesome Cursor Rules ](`#awesome-cursor-rules-`) |
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 55-55: Spaces inside link text
(MD039, no-space-in-links)
🤖 Prompt for AI Agents
In `@README.md` around lines 52 - 55, The Table of Contents contains an external
link entry "Ruleskill" which breaks the README rule that all TOC links must be
relative and must point to actual sections; either remove the "-
[Ruleskill](https://ruleskill.com) - We want to verify your code for the
RuleSkill Protocol. Claim your badge." line from the "Contents" list, or replace
it with a relative anchor that matches a new section heading you add (e.g., add
a "## Ruleskill" section) and place that TOC entry in the correct
alphabetical/category order; update the TOC entry text and anchor so it exactly
matches the new section heading to keep links accurate.
Hi! I found this list very useful. I'd like to contribute 'Ruleskill' - an AI marketing engine for developers. Hope it helps!
Summary by CodeRabbit