vllm-project/semantic-router

feature: Memory Assisted Code Review Bot

Open

#1,902 opened on May 11, 2026

View on GitHub
 (8 comments) (0 reactions) (1 assignee)Go (699 forks)github user discovery
area/agentarea/environmentarea/researcharea/testingarea/tool-managementarea/user-experienceenhancementgood first issuehelp wantedpriority/P1stale

Repository metrics

Stars
 (4,293 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the feature

Since we have many code agent authored PR, we need to have a more streamlined review process to help AI review bot to understand these PRs, especially the internal reasoning of these coding assistant. Most of these internal thinking are in the memory md files.

I checked GitHub marketplace, the existing AI review actions only review the diff. So I am proposing that:

  • customize AI review action
  • require submitting the memory md or revised form (make sure no privacy info is in the md file) in docs directory when submitting a large code change (e.g. >500 LOC)
  • instruct the AI review action to review the diff based on the memory md.
  • publish this customized review action in GitHub marketplace

Primary layer

global level

Why this layer?

Coding agents of different kinds make review process very challenging. At the same time, we are also facing GitHub Copilot review limit. Having a customized review action is the way to go.

Why do you need this feature?

No response

Additional context

No response

Contributor guide

Research direction
Investigate existing AI code review GitHub Actions, understand the memory md file format used by coding agents, and design a custom action that reads the memory md to guide diff review. Ensure privacy by stripping sensitive info from the memory file. Explore GitHub Marketplace publishing steps.
Tech stack
go
Domain
backenddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50