microsoft / microsoft/agentsleague
Project: [Creative App] - [Reviewly]
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 286
- Forks
- 92
- Avg merge
- 12h 44m
- Merged PRs (30d)
- 1
Description
Track
Creative Apps (GitHub Copilot)
Project Name
Reviewly
GitHub Username
@Harsh9485
Repository URL
https://github.com/Harsh9485/Reviewly
Project Description
Reviewly solves a real problem that open source maintainers face every day: deciding which pull requests deserve their time and attention.
In open source projects, many developers contribute. That is a great thing. However, maintainers often receive a large number of pull requests, and not all of them meet the project’s quality standards. Some contributors, especially beginners, rely heavily on AI tools to generate code just to improve their profile. The result is low-effort or poorly aligned pull requests.
Maintainers still have to read the code, understand the changes, test them, and verify that the contribution follows the project guidelines. If the pull request is low quality, this process wastes valuable time and energy.
This is where Reviewly comes in.
Reviewly is an MCP server designed to work directly with GitHub Copilot in VS Code. It analyzes pull requests before a maintainer starts a full review. It evaluates different signals such as:
- Code quality and structure
- Signs of AI-generated low-effort code
- Commit cleanliness and clarity
- PR description quality
- Presence of supporting evidence like screenshots or videos
Reviewly uses a scoring system that aggregates these signals into a structured result. The MCP server collects relevant PR data, processes it through the scoring logic, and then provides the analysis to GitHub Copilot. Copilot uses this structured output to generate a clear recommendation for the maintainer, such as whether the PR looks solid, risky, or likely low quality.
The goal is not to replace human review, but to prioritize attention. Reviewly helps maintainers focus on high-value contributions first and reduce time spent on low-effort pull requests.
You can find more details about the scoring system and detection logic in the project documentation.
Demo Video or Screenshots
https://drive.google.com/file/d/1RGLCeFyQGxEpaW3NHYetWT5GRUQdL0aF/view?usp=sharing
Primary Programming Language
TypeScript/JavaScript
Key Technologies Used
- JavaScript / TypeScript
- GitHub API
- MCP Server
Submission Type
Individual
Team Members
No response
Submission Requirements
- My project meets the track-specific challenge requirements
- My repository includes a comprehensive README.md with setup instructions
- My code does not contain hardcoded API keys or secrets
- I have included demo materials (video or screenshots)
- My project is my own work with proper attribution for any third-party code
- I agree to the Code of Conduct
- I have read and agree to the Disclaimer
- My submission does NOT contain any confidential, proprietary, or sensitive information
- I confirm I have the rights to submit this content and grant the necessary licenses
Quick Setup Summary
Install dependencies
npm install
Build the project
npm run build
Verify build output
ls build/
Output: handlers.js, index.js, schemas.js, types.js
Technical Highlights
**
Challenges & Learnings
MCP
Contact Information
panwarharshwardhan67@gmail.com
Country/Region
India
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the submitted repository's README.md, then run npm install and npm run build; the payload identifies build/handlers.js, index.js, schemas.js, and types.js as outputs. No change request or acceptance criteria is given, so completion cannot be determined from this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript, typescript
- Domain
- ai, api, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100