Skip to content
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.

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

issue chat docs #254

Merged
merged 6 commits into from
Mar 25, 2025
Merged

issue chat docs #254

merged 6 commits into from
Mar 25, 2025

Conversation

alexcoderabbitai
Copy link
Contributor

No description provided.

Copy link
Contributor

coderabbitai bot commented Mar 25, 2025

Walkthrough

A new documentation file, "Issue Chat", has been added under the docs guides. This file details how developers can integrate CodeRabbit’s chat functionalities within GitHub and GitLab issues by mentioning a bot. It explains features such as code analysis, agentic thought chain processing, command line tool access, repository historical insights, and various use cases. The document also provides examples, images, and best practices for effective use.

Changes

File Summary
docs/guides/issue-chat.md Added a new documentation file outlining how to use CodeRabbit’s chat interface in issue comments, covering features like code analysis, agentic thought chain, and more.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant IT as Issue Tracker (GitHub/GitLab)
    participant Bot as CodeRabbit Bot
    participant CI as Chat Interface

    Dev->>IT: Post issue comment mentioning @CodeRabbitBot
    IT->>Bot: Forward comment to CodeRabbit Bot
    Bot->>CI: Process natural language query
    CI-->>Bot: Return analysis and response details
    Bot-->>IT: Post formatted response in issue comment
Loading

Possibly related PRs

  • Agent chat docs #248: Introduces documentation for "Agentic Chat", another chat functionality feature that supports user interactions via issue comments.
  • adding guide on issue creation #250: Adds a guide on issue creation through the chat interface, enhancing user interaction with CodeRabbit's issue management features.

Poem

I'm a rabbit hopping in delight,
New "Issue Chat" shines so bright.
With CodeRabbit bot in issue threads,
I nibble on knowledge as it spreads.
Hop on over, let's chat away—
In docs and code, we brighten the day!
🐇✨


🪧 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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

Copy link

cloudflare-workers-and-pages bot commented Mar 25, 2025

Deploying coderabbit-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 47f982d
Status: ✅  Deploy successful!
Preview URL: https://68e7d9ac.coderabbit-docs.pages.dev
Branch Preview URL: https://feat-issue-chat-documentatio.coderabbit-docs.pages.dev

View logs

@alexcoderabbitai alexcoderabbitai marked this pull request as ready for review March 25, 2025 16:03
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

🧹 Nitpick comments (6)
docs/guides/issue-chat.md (6)

14-17: Enhance Compound Adjective Formatting in Introduction
In line 16, the phrase "create AI powered code searches" should use a hyphen for the compound adjective. Consider updating it as follows:

- create AI powered code searches
+ create AI-powered code searches

Additionally, you might consider whether a more emphatic adjective could further strengthen the description, but the current wording is acceptable if preferred.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~16-~16: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... code, get answers to questions, create AI powered code searches, plan features, and gain ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~16-~16: Consider an alternative adjective to strengthen your wording.
Context: ... code searches, plan features, and gain deeper insights into their codebase - all with...

(DEEP_PROFOUND)


18-20: Consider Preposition Adjustment in Getting Started Section
The sentence "To start a conversation with CodeRabbit in any issue:" may be clearer with a slight preposition change. For example:

- To start a conversation with CodeRabbit in any issue:
+ To start a conversation with CodeRabbit on any issue:

This change might better reflect the context in which the conversation is initiated.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~20-~20: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...To start a conversation with CodeRabbit in any issue: 1. Simply mention `@coderab...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)


46-54: Correct Compound Adjective in Capability Description
Within the list under "This allows CodeRabbit to:", the bullet "Create AI powered code searches" should be updated with proper hyphenation:

-    - Create AI powered code searches
+    - Create AI-powered code searches

This ensures that the compound adjective is correctly formatted.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~52-~52: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...are answers about the codebase - Create AI powered code searches - Use tribal knowledge fr...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


80-82: Hyphenate Compound Adjective in Open Source Support Section
The sentence "CodeRabbit can help maintain open source projects by:" should hyphenate "open source" when used as a compound adjective. A suggested update would be:

-    CodeRabbit can help maintain open source projects by:
+    CodeRabbit can help maintain open-source projects by:

This adjustment aligns with common style guidelines.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~80-~80: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ning.png) ## Additional Use Cases ### Open Source Support CodeRabbit can help maintain o...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e Support CodeRabbit can help maintain open source projects by: - Answering common suppor...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


95-101: Hyphenate Compound Adjective in Documentation Assistance
Under the "Documentation Assistance" section, change "Generate high level documentation" to use a hyphen in "high-level":

-    - Generate high level documentation
+    - Generate high-level documentation

This refines the readability and adheres to standard English compound adjective rules.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~97-~97: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...istance Use issue chat to: - Generate high level documentation - Create usage examples a...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


147-155: Fix Hyphenation for Compound Adjective in Best Practices
In the Best Practices section, on the bullet that advises "ask follow up questions," update the phrase to "ask follow-up questions" for proper hyphenation:

-       - Use multiple messages to ask follow up questions if needed
+       - Use multiple messages to ask follow-up questions if needed

This improvement ensures stylistic consistency across the document.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fe42e21 and f7a09e6.

⛔ Files ignored due to path filters (9)
  • static/img/guides/agentic-thought-chain.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/chat-example.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/chat-learnings-use.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/chat-script-execution.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/feature-planning.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/gitlab-issue-chat.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/high-level-docs.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/marketing-posts.png is excluded by !**/*.png, !**/*.png
  • static/img/guides/open-source-support.png is excluded by !**/*.png, !**/*.png
📒 Files selected for processing (1)
  • docs/guides/issue-chat.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/guides/issue-chat.md

[uncategorized] ~16-~16: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... code, get answers to questions, create AI powered code searches, plan features, and gain ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~16-~16: Consider an alternative adjective to strengthen your wording.
Context: ... code searches, plan features, and gain deeper insights into their codebase - all with...

(DEEP_PROFOUND)


[uncategorized] ~20-~20: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...To start a conversation with CodeRabbit in any issue: 1. Simply mention `@coderab...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)


[uncategorized] ~52-~52: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...are answers about the codebase - Create AI powered code searches - Use tribal knowledge fr...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~80-~80: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ning.png) ## Additional Use Cases ### Open Source Support CodeRabbit can help maintain o...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e Support CodeRabbit can help maintain open source projects by: - Answering common suppor...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~97-~97: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...istance Use issue chat to: - Generate high level documentation - Create usage examples a...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[grammar] ~144-~144: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ... ones - Use multiple messages to ask follow up questions if needed ## Related Resourc...

(CA_FOLLOW_UP)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (2)
docs/guides/issue-chat.md (2)

1-6: YAML Front Matter Structured Correctly
The front matter is clear and well-defined, with an appropriate title, sidebar label, description, and position for the document.


8-12: MDX Code Block Implementation Looks Good
The MDX code block properly imports the ProPlanNotice component and renders it.

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

🧹 Nitpick comments (6)
docs/guides/issue-chat.md (6)

14-17: Introduction Clarity & Compound Adjective Hyphenation.
The introductory section is comprehensive and clearly outlines the capabilities. However, on line 16, consider hyphenating compound adjectives for clarity. For example, change “AI powered code searches” to “AI-powered code searches.”

🧰 Tools
🪛 LanguageTool

[uncategorized] ~16-~16: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... code, get answers to questions, create AI powered code searches, plan features, and gain ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~16-~16: Consider an alternative adjective to strengthen your wording.
Context: ... code searches, plan features, and gain deeper insights into their codebase - all with...

(DEEP_PROFOUND)


18-20: Preposition Choice in Instructions.
The “Getting Started” section is easy to follow. One minor suggestion: on line 20, consider replacing “in any issue” with “on any issue” for improved clarity when referring to comment threads.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~20-~20: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...To start a conversation with CodeRabbit in any issue: 1. Simply mention `@coderab...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)


52-52: Hyphenate Compound Adjectives in Bullet Points.
In the “Core Capabilities” section, the bullet point “Create AI powered code searches” on line 52 should use a hyphen, i.e. “AI-powered code searches,” to follow style conventions.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~52-~52: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...are answers about the codebase - Create AI powered code searches - Use tribal knowledge fr...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


80-82: Hyphenation for Compound Modifiers.
Within the “Open Source Support” section (lines 80–82), consider hyphenating “open source projects” to “open-source projects” since it acts as a compound adjective.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~80-~80: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ning.png) ## Additional Use Cases ### Open Source Support Issue chat, like all Pro CodeR...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ll Pro CodeRabbit features, is free for open source projects. CodeRabbit acts as a powerful...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...bit acts as a powerful support tool for open source maintainers by: - Answering common use...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


97-101: Improve Compound Adjective Formatting.
In the “Documentation Assistance” section, change “high level descriptions” and “high level documentation” to “high-level descriptions” and “high-level documentation” respectively for better readability.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~99-~99: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... Assistance Use issue chat to generate high level descriptions of the code and services i...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~101-~101: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...n.so/help/guides) and more: - Generate high level documentation - Create usage examples a...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


148-149: Grammar: Hyphenate “Follow-up.”
In the Best Practices section (lines 148–149), change “follow up questions” to “follow-up questions” to comply with compound adjective conventions.

🧰 Tools
🪛 LanguageTool

[grammar] ~148-~148: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ... ones - Use multiple messages to ask follow up questions if needed ## Related Resourc...

(CA_FOLLOW_UP)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7a09e6 and 47f982d.

📒 Files selected for processing (1)
  • docs/guides/issue-chat.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/guides/issue-chat.md

[uncategorized] ~16-~16: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... code, get answers to questions, create AI powered code searches, plan features, and gain ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~16-~16: Consider an alternative adjective to strengthen your wording.
Context: ... code searches, plan features, and gain deeper insights into their codebase - all with...

(DEEP_PROFOUND)


[uncategorized] ~20-~20: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...To start a conversation with CodeRabbit in any issue: 1. Simply mention `@coderab...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)


[uncategorized] ~52-~52: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...are answers about the codebase - Create AI powered code searches - Use tribal knowledge fr...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~80-~80: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ning.png) ## Additional Use Cases ### Open Source Support Issue chat, like all Pro CodeR...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ll Pro CodeRabbit features, is free for open source projects. CodeRabbit acts as a powerful...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...bit acts as a powerful support tool for open source maintainers by: - Answering common use...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~99-~99: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... Assistance Use issue chat to generate high level descriptions of the code and services i...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~101-~101: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...n.so/help/guides) and more: - Generate high level documentation - Create usage examples a...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[grammar] ~148-~148: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ... ones - Use multiple messages to ask follow up questions if needed ## Related Resourc...

(CA_FOLLOW_UP)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (3)
docs/guides/issue-chat.md (3)

1-7: Front Matter Completeness.
The front matter is clear and well-organized with title, sidebar_label, description, and sidebar_position. Consider adding additional metadata (e.g., author or date) if your site guidelines require it.


8-13: MDX Code Block Validation.
The MDX code block correctly imports and renders the ProPlanNotice component. Please verify that the component path (@site/src/components/ProPlanNotice.mdx) is correct and that the component is available in the specified directory.


1-156: Overall Documentation Quality.
The new “Issue Chat” documentation is comprehensive, well-structured, and enriched with useful examples and visuals. Addressing the minor stylistic nitpicks—especially around compound adjectives and preposition use—will further enhance clarity and professionalism.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~16-~16: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... code, get answers to questions, create AI powered code searches, plan features, and gain ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~16-~16: Consider an alternative adjective to strengthen your wording.
Context: ... code searches, plan features, and gain deeper insights into their codebase - all with...

(DEEP_PROFOUND)


[uncategorized] ~20-~20: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...To start a conversation with CodeRabbit in any issue: 1. Simply mention `@coderab...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)


[uncategorized] ~52-~52: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...are answers about the codebase - Create AI powered code searches - Use tribal knowledge fr...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~80-~80: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ning.png) ## Additional Use Cases ### Open Source Support Issue chat, like all Pro CodeR...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ll Pro CodeRabbit features, is free for open source projects. CodeRabbit acts as a powerful...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...bit acts as a powerful support tool for open source maintainers by: - Answering common use...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~99-~99: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... Assistance Use issue chat to generate high level descriptions of the code and services i...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~101-~101: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...n.so/help/guides) and more: - Generate high level documentation - Create usage examples a...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[grammar] ~148-~148: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ... ones - Use multiple messages to ask follow up questions if needed ## Related Resourc...

(CA_FOLLOW_UP)

@alexcoderabbitai alexcoderabbitai merged commit de51787 into main Mar 25, 2025
4 checks passed
@alexcoderabbitai alexcoderabbitai deleted the feat/issue-chat-documentation branch March 25, 2025 16:39
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