Skip to content

Add Ruleskill to the list#165

Open
mrkenzi wants to merge 1 commit intoPatrickJS:mainfrom
mrkenzi:add-ruleskill-1770863833
Open

Add Ruleskill to the list#165
mrkenzi wants to merge 1 commit intoPatrickJS:mainfrom
mrkenzi:add-ruleskill-1770863833

Conversation

@mrkenzi
Copy link

@mrkenzi mrkenzi commented Feb 12, 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 reference to the README Contents section.
    • Updated README formatting for improved readability.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 12, 2026

📝 Walkthrough

Walkthrough

A README documentation update that adds a Ruleskill entry to the Contents section and reformats the License line from a Markdown list item to regular text.

Changes

Cohort / File(s) Summary
Documentation Update
README.md
Added Ruleskill link to Contents section; reformatted License section line from list item (dash-prefixed) to regular text formatting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A link to ruleskill hops into view,
The Contents list gets something new,
License formatting takes a fresh turn,
Small tweaks that make the README burn! ✨

🚥 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 describes the main change: adding a new Ruleskill entry to the Contents section of the README.
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

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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: 2

🤖 Fix all issues with AI agents
In `@README.md`:
- Line 351: The license line in README.md was changed from a list item to plain
text; restore consistent list formatting by reverting that line back to a
markdown list item (add the leading "- " so it matches other list entries) or,
if the change was intentional, update the PR description/commit message to
explicitly state the formatting decision; target the single line containing the
CC0 badge and adjust it in the README.md to maintain uniform list formatting
across the file.
- Line 54: The README's Contents (Table of Contents) currently includes an
external "Ruleskill" link which doesn't belong in internal navigation; remove
the Ruleskill entry from the Contents section and instead add the Ruleskill link
into the appropriate spot per the PR guidance (either append it to the
Directories section near the existing Directories list, create a new "Tools" or
"Resources" section and add it there, or add it under "Rules" only if you
include a .cursorrules file), update any anchors or headings as needed, and
ensure the link follows the repo guideline by using a relative link where
applicable and matching the README's existing structure and formatting.


## Contents

- [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge.
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 | 🔴 Critical

Incorrect placement: External link in Contents/Table of Contents section.

The Contents section is a table of contents for navigating the README structure, with internal anchor links to sections like #rules, #contributing, etc. The Ruleskill entry is an external link that doesn't fit this purpose.

Based on the PR description and the nature of Ruleskill, consider these alternatives:

  1. Add to the Directories section (around line 293) if Ruleskill is a directory/listing service for cursor rules
  2. Create a new "Tools" or "Resources" section if Ruleskill is a related tool/service
  3. Add to Rules section only if you're including an actual .cursorrules file in a new folder per the Contributing guidelines

As per coding guidelines: "Maintain the existing structure of the README.md file" and "Ensure all links in the README.md file are relative and correct."

📝 Example: Adding to Directories section

If Ruleskill is a directory/listing service, add it to the Directories section instead:

 ## Directories
 
 - [CursorList](https://cursorlist.com)
 - [CursorDirectory](https://cursor.directory/)
+- [Ruleskill](https://ruleskill.com) - AI marketing engine for developers

Remove it from the Contents section:

 ## Contents
 
-- [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge.
 - [Awesome Cursor Rules ](`#awesome-cursor-rules-`)
🤖 Prompt for AI Agents
In `@README.md` at line 54, The README's Contents (Table of Contents) currently
includes an external "Ruleskill" link which doesn't belong in internal
navigation; remove the Ruleskill entry from the Contents section and instead add
the Ruleskill link into the appropriate spot per the PR guidance (either append
it to the Directories section near the existing Directories list, create a new
"Tools" or "Resources" section and add it there, or add it under "Rules" only if
you include a .cursorrules file), update any anchors or headings as needed, and
ensure the link follows the repo guideline by using a relative link where
applicable and matching the README's existing structure and formatting.

## License

[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/) No newline at end of file
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 | 🟡 Minor

Formatting change: License line changed from list item to regular text.

The License line was changed from a list item format (with - prefix) to regular text. While this might be intentional since there's only one item, it changes the existing formatting pattern without clear rationale.

Was this change intentional? If so, please confirm. Otherwise, consider maintaining the original list format for consistency.

As per coding guidelines: "Use consistent formatting for list items in the README.md file."

↩️ Revert to original formatting
 ## License
 
-[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
+- [![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
📝 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
[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
## License
- [![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
🤖 Prompt for AI Agents
In `@README.md` at line 351, The license line in README.md was changed from a list
item to plain text; restore consistent list formatting by reverting that line
back to a markdown list item (add the leading "- " so it matches other list
entries) or, if the change was intentional, update the PR description/commit
message to explicitly state the formatting decision; target the single line
containing the CC0 badge and adjust it in the README.md to maintain uniform list
formatting across the file.

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