Community tweak

[hannesrudolph]

Removed Roo Flow from docs/community.md

Roo Flow was removed from the community projects list because it utilizes the 'Footgun Prompting' feature (docs/features/footgun-prompting.md). This feature allows overriding system prompts, which requires the Roo Flow system prompt to be updated whenever improvements are made to Roo Code's core prompting to prevent breaking user experiences. To simplify maintenance and avoid potential issues for users, the project has been removed from the featured list.

Important

Removes the Roo Flow project section from docs/community.md.

• Documentation:
  • Removes the section on the Roo Flow project from docs/community.md, including its description and key improvements.
  • Deletes two blank lines in docs/community.md for formatting consistency.

^{This description was created by for bf025e6. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
roo-code-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 18, 2025 5:40pm

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to bf025e6 in 2 minutes and 15 seconds

More details

• Looked at 34 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 6 drafted comments based on config settings.

1. docs/community.md:159

• Draft comment:
  Duplicate 'Orchestrator' sections: one by @mrubens and one by @iiwish. Consider clarifying the distinctions (or renaming one) to avoid confusion for the reader.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

2. docs/community.md:37

• Draft comment:
  Consider enforcing consistent JSON formatting across mode definitions using a formatter like Prettier to maintain style and readability.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

3. docs/community.md:14

• Draft comment:
  Removal of the 'Roo Flow Project by @GreatScottyMac' section may require justification. Ensure this removal is intended and update related documentation if needed.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to ensure the removal is intended and to update documentation, which violates the rules against asking for confirmation of intention and updating documentation. It doesn't provide a specific code suggestion or point out a specific issue with the code.

4. docs/community.md:1

• Draft comment:
  The PR title 'Community tweak' and missing description do not explain the rationale for these changes. Please provide a more descriptive title and detailed PR description per our development standards.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

5. docs/community.md:77

• Draft comment:
  Typo: In the Documentation Writer section (line 77), consider changing "A mode that is specialized technical documentation expert" to "A mode that is a specialized technical documentation expert" for improved clarity.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

6. docs/community.md:23

• Draft comment:
  Typo: In the Roo Code Dynamic Rules section (line 23), change "on Github" to "on GitHub" for consistency.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_wHsMCQ5SD1t8PkGo

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[hannesrudolph]

@mrubens please review.

[GreatScottyMac]

Makes sense!