Skip to content

Add repo-seatbelt to Utilities#274

Open
berkcangumusisik wants to merge 1 commit intoPatrickJS:mainfrom
berkcangumusisik:main
Open

Add repo-seatbelt to Utilities#274
berkcangumusisik wants to merge 1 commit intoPatrickJS:mainfrom
berkcangumusisik:main

Conversation

@berkcangumusisik
Copy link
Copy Markdown

@berkcangumusisik berkcangumusisik commented May 3, 2026

What

repo-seatbelt auto-generates .cursorrules (and 6 other AI rule files) from a single config that reflects what's actually sensitive in your repo — auth, payment, migrations, env, production config.

Why it belongs in Utilities

It doesn't ship a stack-specific .cursorrules like most entries; instead it's a tool that generates them on demand for any project. This matches the precedent of Cursor Watchful Headers — the only other external-tool entry in this section.

Project facts

  • License: MIT
  • npm: https://www.npmjs.com/package/repo-seatbelt
  • Six built-in project presets (Next.js + Stripe, Django, Rails, Expo, FastAPI, monorepos)
  • Generates .cursorrules, .windsurfrules, .clinerules, .rules, CLAUDE.md, AGENTS.md, CONVENTIONS.md

Summary by CodeRabbit

  • Documentation
    • Added information about repo-seatbelt utility to the README's Utilities section, detailing its functionality for auto-generating configuration files and providing server guardrails.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 3, 2026

📝 Walkthrough

Walkthrough

The PR adds a single entry to the "Utilities" section of README.md: repo-seatbelt, a tool that auto-generates .cursorrules and related configuration files from repository structure, including MCP server support and pre-commit hooks.

Changes

Documentation Update

Layer / File(s) Summary
Utilities Section
README.md
Added repo-seatbelt entry to the Utilities list, describing its functionality for auto-generating .cursorrules and related files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • PatrickJS

Poem

🐰 A seatbelt tool springs into view,
Cursorrules auto-crafted anew,
Repos tidy, rules so bright,
Guards and configs—shining light! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add repo-seatbelt to Utilities' directly and accurately describes the main change: adding a new resource entry to the Utilities section of the README.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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
Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.

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

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

Copy link
Copy Markdown
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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 294: Replace the absolute external URL in the README list item for
"[repo-seatbelt]" with a repository-relative link pointing to the local
documentation page for that utility (e.g., ./utilities/repo-seatbelt.md or
./docs/repo-seatbelt.md); update the "[repo-seatbelt]" markdown link target in
README.md accordingly and, if the external GitHub URL must still be referenced,
move that full URL into the referenced local page (repo-seatbelt doc) instead of
using it directly in README.
🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 78bafb13-efac-474d-9b97-a0cb0f321dde

📥 Commits

Reviewing files that changed from the base of the PR and between 8477f22 and 710a3e3.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md

- [Cursor Watchful Headers](https://github.com/johnbenac/cursor-watchful-headers) - A Python-based file watching system that automatically manages headers in text files and maintains a clean, focused project tree structure. Perfect for maintaining consistent file headers and documentation across your project, with special features to help LLMs maintain better project awareness.
- [Helium MCP (news, bias, markets, options, memes)](./rules/helium-mcp-cursorrules-prompt-file/.cursorrules) - Cursor rules for using Helium MCP in Cursor: streamable HTTP setup, when to call each hosted tool (`search_news`, `search_balanced_news`, `get_source_bias`, `get_bias_from_url`, `get_all_source_biases`, `get_ticker`, `get_option_price`, `get_top_trading_strategies`, `search_memes`), query discipline, and rate-limit awareness. See also `./rules/helium-mcp-cursorrules-prompt-file/README.md`.
- [repo-seatbelt](https://github.com/berkcangumusisik/repo-seatbelt) - A CLI that auto-generates `.cursorrules` (and CLAUDE.md, .windsurfrules, AGENTS.md, etc.) from your repo's structure — detects auth, payment, migrations, env files, and writes safety rules tailored to what's actually sensitive. Ships project presets for Next.js + Stripe, Django, Rails, Expo, FastAPI, and monorepos. Also runs as an MCP server for runtime guardrails and installs a pre-commit hook that blocks high-risk commits.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use a repository-relative link for this new Utilities entry.

Line 294 adds an absolute external URL; this violates the README link rule for relative links. Please point this item to a relative path in-repo (and reference external URLs from that page if needed).

As per coding guidelines, "Ensure all links in the README.md file are relative and correct".

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 294, Replace the absolute external URL in the README list
item for "[repo-seatbelt]" with a repository-relative link pointing to the local
documentation page for that utility (e.g., ./utilities/repo-seatbelt.md or
./docs/repo-seatbelt.md); update the "[repo-seatbelt]" markdown link target in
README.md accordingly and, if the external GitHub URL must still be referenced,
move that full URL into the referenced local page (repo-seatbelt doc) instead of
using it directly in README.

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