additional column for tool table

[cr-ruhanmuzaffar]

No description provided.

[coderabbitai]

Walkthrough

The documentation for supported tools in CodeRabbit has been updated to include a new "Category" column in the tools table. This column categorizes each tool based on its primary function, such as "Code Quality," "Code Security," and "Grammar Checking." The overall structure of the document remains unchanged, with existing sections on enabling/disabling tools, customizing strictness, and checking tool output.

Changes

File	Change Summary
docs/tools/tools.md	Added a new "Category" column to the tools table for categorization of tools based on function.

Possibly related PRs

• docs: enhance Support, Features, and Intro pages; improve image SEO, internal linking, clarity, and layout. #115: The changes in the main PR regarding the documentation of tools and their categorization may relate to the enhancements made in the docs/about/features.md file, which also focuses on improving the clarity and presentation of features related to CodeRabbit.

Suggested reviewers

• dk03051996
• MonRay2024
• tyaga001

Poem

In the land of CodeRabbit, tools now shine,
With categories clear, their functions align.
From quality checks to security tight,
Each tool has a place, making work light!
Hopping through code, we celebrate this feat,
Clarity and purpose, oh what a treat! 🐇✨

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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 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.

[cloudflare-workers-and-pages]

Deploying coderabbit-docs with    Cloudflare Pages

Latest commit:	4e39aae
Status:	✅  Deploy successful!
Preview URL:	https://815bdb5f.coderabbit-docs.pages.dev
Branch Preview URL:	https://ruhan-tools-col.coderabbit-docs.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

docs/tools/tools.md (2)

55-55: Unify grammar checking category names.

There's an inconsistency in how the grammar checking category is named:

• Line 55: "Grammar Checking"
• Line 57: "Grammar and Spell Checking"

Please standardize these to use the same category name throughout the table.

Also applies to: 57-57

---

39-39: Consider adding context about categories.

The new Category column would benefit from a brief introduction in the documentation above the table, explaining how these categories are determined and their significance in tool selection.

Consider adding a paragraph before the table:

## Supported Tools

+CodeRabbit's tools are categorized based on their primary function, such as Code Quality, Security Analysis, and Grammar Checking. This categorization helps you choose the right tools for your specific needs.
+
| Technology                  | Tools                                                      | Category                       |

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 522ebdf and 6b0e38e.

📒 Files selected for processing (1)

• docs/tools/tools.md (1 hunks)

🔇 Additional comments (1)

docs/tools/tools.md (1)

39-69: LGTM! Well-structured table with clear categorization.

The table is well-formatted with proper alignment and clear categorization of tools. The categories are logically assigned and provide valuable context about each tool's primary function. Multi-category tools are properly handled with comma separation.