Skip to content

Conversation

@mrkenzi
Copy link

@mrkenzi mrkenzi commented Feb 5, 2026

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

  • Documentation
    • Added Ruleskill link to the Contents section in README.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 5, 2026

📝 Walkthrough

Walkthrough

The 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

Cohort / File(s) Summary
Documentation
README.md
Added Ruleskill link entry to Contents section with descriptive text; license entry unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A link for Ruleskill hops into view,
Contents grow richer, the doc shines anew,
With whiskers twitched and README care,
This simple addition floats light on the air! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add Ruleskill to the list' directly and clearly summarizes the main change—adding a new item (Ruleskill) to the repository's contents list, which aligns with the pull request objectives and file modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment on lines 52 to 55
## Contents

- [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge.
- [Awesome Cursor Rules ](#awesome-cursor-rules-)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

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.

Suggested change
## 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant