Skip to content

Remove new line in rules, Remove duplicate Roo option #484

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove new line in rules, Remove duplicate Roo option #484

wants to merge 1 commit into from
+1 −3

Conversation

tanjunior
Copy link

@tanjunior tanjunior commented Aug 9, 2025 •
edited by coderabbitai bot
Loading

Summary by CodeRabbit

  • Bug Fixes

    • Corrected a command usage example in the documentation by merging a split line into a single, continuous line for improved clarity.

  • Chores

    • Removed the "Roo" editor option from the list of available editors.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Aug 9, 2025

⚠️ No Changeset found

Latest commit: 457217b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 9, 2025 •
edited
Loading

Walkthrough

This change removes the "Roo" editor entry from a CLI helper constant and corrects a line break in a markdown template for addon instructions, merging a split command example into a single line. No modifications to logic, control flow, or public API declarations were made.

Changes

Cohort / File(s) Change Summary
Editor Constant Update
apps/cli/src/helpers/setup/vibe-rules-setup.ts		 Removed the "roo" key (label "Roo", hint ".clinerules/*.md") from the EDITORS constant object.
Template Command Formatting
apps/cli/templates/addons/vibe-rules/.bts/rules.md.hbs		 Merged a broken command usage example into a single line, preserving conditional logic for prefixes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hopped through code today,
Tidying up the Roo away.
A command line, once split in two,
Now stands together, clear and true.
With every change, both small and neat,
The codebase grows more light and sweet!
🐇✨

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • 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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot]
coderabbitai bot reviewed Aug 9, 2025
View reviewed changes
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: 0

🔭 Outside diff range comments (1)
apps/cli/templates/addons/vibe-rules/.bts/rules.md.hbs (1)

101-104: Broken command in fenced block — merge into a single line for copy-paste

The add command is split across two lines, which will break when users copy-paste. Merge into one line to match the new bullet and the PR objective.

Apply this diff:

 ```bash
-{{#if (eq packageManager "bun")}}bunx{{else if (eq packageManager "pnpm")}}pnpx{{else}}npx{{/if}} create-better-t-stack
-add
+{{#if (eq packageManager "bun")}}bunx{{else if (eq packageManager "pnpm")}}pnpx{{else}}npx{{/if}} create-better-t-stack add

</blockquote></details>

</blockquote></details>

<details>
<summary>🧹 Nitpick comments (1)</summary><blockquote>

<details>
<summary>apps/cli/templates/addons/vibe-rules/.bts/rules.md.hbs (1)</summary><blockquote>

`97-106`: **Avoid duplication of the same command in two places**

You now show the same add command in both a fenced block and a bullet. Consider keeping just one, or extract the conditional runner prefix into a reusable partial to prevent future drift.



Also applies to: 131-131

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**


<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between ea908ddc86e874b9456a660bf2904481a2d3af5f and 457217bfd4a27814c906178ab198602061b1a568.

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `apps/cli/src/helpers/setup/vibe-rules-setup.ts` (0 hunks)
* `apps/cli/templates/addons/vibe-rules/.bts/rules.md.hbs` (1 hunks)

</details>

<details>
<summary>💤 Files with no reviewable changes (1)</summary>

* apps/cli/src/helpers/setup/vibe-rules-setup.ts

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>apps/cli/templates/addons/vibe-rules/.bts/rules.md.hbs (1)</summary>

`131-131`: **LGTM — clear, single-line instruction**

Good addition; consistent conditional runner and single-line copy-pasteable command.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

@AmanVarshney01
Copy link
Owner

Why remove roo when its an available option in vieb-rules 🤔

image

https://www.npmjs.com/package/vibe-rules

@tanjunior
Copy link
Author

From what I tested, the cli options roo and cline/roo creates the same files. Or maybe I was mistaken about it, correct me if I am wrong.

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

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@tanjunior @AmanVarshney01