Add Survivor Forge to Directories#191
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughREADME.md updated: the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
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.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
README.md (1)
290-294: 🛠️ Refactor suggestion | 🟠 MajorReorder entries alphabetically to comply with guidelines.
The new entry is positioned correctly relative to existing entries, but the Directories section should be fully alphabetically ordered. As per coding guidelines, "Maintain alphabetical order within each category in the README.md file".
📝 Proposed fix to alphabetize all Directories entries
## Directories -- [CursorList](https://cursorlist.com) - [CursorDirectory](https://cursor.directory/) +- [CursorList](https://cursorlist.com) - [Survivor Forge Cursor Rules](https://github.com/survivorforge/cursor-rules) - A collection of .cursorrules files covering 16 frameworks including React, Next.js, Python, Go, Rust, Flutter, and more.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 290 - 294, The "Directories" section is not fully alphabetized; reorder the list items under the "## Directories" header so the entries (e.g., "CursorList", "CursorDirectory", "Survivor Forge Cursor Rules") are sorted alphabetically by their displayed link text, preserving each item's link/URL and punctuation exactly as written and updating the block so the sequence is strictly alphabetical.
🧹 Nitpick comments (1)
README.md (1)
294-294: Consider adding descriptions to other Directories entries for consistency.The new entry includes a helpful description, while the existing CursorList and CursorDirectory entries do not. Adding brief descriptions to all entries would improve consistency and provide users with more context.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` at line 294, The README adds a description for "Survivor Forge Cursor Rules" but the other directory entries lack descriptions; update the README.md to add brief, consistent descriptions for the existing "CursorList" and "CursorDirectory" entries (matching the tone/length of the new Survivor Forge line) so each directory entry includes a one-line summary of what the repository/content provides.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@README.md`:
- Around line 290-294: The "Directories" section is not fully alphabetized;
reorder the list items under the "## Directories" header so the entries (e.g.,
"CursorList", "CursorDirectory", "Survivor Forge Cursor Rules") are sorted
alphabetically by their displayed link text, preserving each item's link/URL and
punctuation exactly as written and updating the block so the sequence is
strictly alphabetical.
---
Nitpick comments:
In `@README.md`:
- Line 294: The README adds a description for "Survivor Forge Cursor Rules" but
the other directory entries lack descriptions; update the README.md to add
brief, consistent descriptions for the existing "CursorList" and
"CursorDirectory" entries (matching the tone/length of the new Survivor Forge
line) so each directory entry includes a one-line summary of what the
repository/content provides.
Adds Survivor Forge Cursor Rules to the Directories section.
The repo contains .cursorrules files for 16 frameworks/languages: React, Next.js, Python (Django, FastAPI), Go, Rust, Flutter, SvelteKit, Node.js/Express, TypeScript, Tailwind CSS, Supabase, Docker/DevOps, AWS Serverless, Chrome Extensions, and LangChain.
Each file follows the same format used in this repo — practical rules covering code style, architecture patterns, error handling, and testing conventions for each framework.
Happy to adjust the entry wording if needed.
Summary by CodeRabbit