Skip to content

Commit 677c570

Browse files
authored
Update Future-Developments.md
1 parent beb6b6c commit 677c570

File tree

1 file changed

+25
-31
lines changed

1 file changed

+25
-31
lines changed

docs/about/Future-Developments.md

+25-31
Original file line numberDiff line numberDiff line change
@@ -4,65 +4,59 @@ sidebar_label: Future Development
44
description: Learn how CodeRabbit works in a pull request review.
55
---
66

7-
# 🚀 Future Developments
7+
# Future Developments
88

99
We are actively iterating and refining CodeRabbit, and this is a sneak peek into the upcoming milestones and releases. We are focused on making the Applied AI review better than the median manual review. In addition to that, we are looking at a holistic user experience with various integrations and types of reviews.
1010

11-
## 🧠 Applied AI Improvements
11+
## Applied AI Improvements
1212

1313
We are actively trying to make the application of Generative AI more useful , relevant , meaningful for the coder and reviewer journey. Our immediate focus is
1414

15-
### 🎯 Accuracy and Conciseness Enhancements
15+
### Accuracy and Conciseness Enhancements
1616

17-
- 📝 Refining knowledge base context understanding
18-
- 📊 Implementing advanced summarization techniques
19-
- 🔄 Implementing a knowledge base feature library
17+
- Refining knowledge base context understanding
18+
- Implementing advanced summarization techniques
19+
- Implementing a knowledge base feature library
2020

21-
### 🧠 Learning Refinements
21+
### Learning Refinements
2222

23-
- 🔁 We have made significant improvement of the learning Enhancing reinforcement learning based on the user feedback
23+
- We have made significant improvement of the learning Enhancing reinforcement learning based on the user feedback
2424

25-
## 🌟 New Feature Enhancements
25+
## New Feature Enhancements
2626

27-
### 🔗 Expanded Integrations
27+
### Expanded Integrations
2828

2929
We are integrating various tool chains to enable coders and reviewers to have a consistent experience irrespective of the tools. The immediate tools would be:
3030

31-
- 🦊 **Bitbucket**
32-
- 🔄 **Circle CI**
33-
- 👨‍🔧 **Jenkins**
31+
- **Circle CI**
32+
- **Jenkins**
3433

35-
### 💬 Communication Tool Integrations
34+
### Communication Tool Integrations
3635

3736
Communication and the user experience of review via various communication tools are going to be key. We will start with integrations to Slack and Microsoft Teams and will be diving into the design engineering of these flows further:
3837

39-
- 💬 **Slack**: Real-time notifications and interactive discussions
40-
- 👥 **Microsoft Teams**: Code review conversations within Microsoft ecosystem
38+
- **Slack**: Real-time notifications and interactive discussions
39+
- **Microsoft Teams**: Code review conversations within Microsoft ecosystem
4140

42-
### 🔍 Enhanced Review Capabilities
41+
### Enhanced Review Capabilities
4342

4443
These are additional capabilities that can also be reviewed in the same PR to accelerate the coder and reviewer journey. This includes pipeline failure analysis and resolution, as well as vulnerability assessment.
4544

46-
#### 1. 🔬 Pipeline Failure Analysis
45+
#### Pipeline Failure Analysis
4746

48-
- 🚨 Automated analysis of CI/CD pipeline failures
49-
- 💡 AI-driven suggestions for resolving issues
50-
- 📊 Historical tracking of pipeline performance
47+
- Automated analysis of CI/CD pipeline failures
48+
- AI-driven suggestions for resolving issues
49+
- Historical tracking of pipeline performance
5150

52-
#### 2. 🛡️ SAST (Static Application Security Testing) Integration
53-
54-
- 🔒 Security-focused code reviews
55-
- 📋 Custom rule sets for different security standards
56-
57-
### 🚀 Finishing Touches
51+
### Finishing Touches
5852

5953
Finishing touches are about experience that often take developers time away from what they like doing best - coding. But adding finishing touches is crucial and should follow the ontology and taxonomy. We will start by looking into Docstring and expand to various areas to solve pain points for coders and reviewers.
6054

61-
#### 1. 📝 DocString Review
55+
#### 1. DocString Review
6256

63-
- Automated checks for docstring presence and quality
64-
- 💡 AI-powered suggestions for improving documentation
65-
- 🎨 Resolving Doc-string conflicts in a following PR
57+
- Automated checks for docstring presence and quality
58+
- AI-powered suggestions for improving documentation
59+
- Resolving Doc-string conflicts in a following PR
6660

6761
> Disclaimer: any product roadmap features mentioned below are only meant to outline
6862
> our general product direction. This documentation is for informational purposes

0 commit comments

Comments
 (0)