Skip to content

Add PR review agent#7516

Draft
Nigusu-Allehu wants to merge 1 commit into
devfrom
dev-nyenework-pr-agent
Draft

Add PR review agent#7516
Nigusu-Allehu wants to merge 1 commit into
devfrom
dev-nyenework-pr-agent

Conversation

@Nigusu-Allehu

Copy link
Copy Markdown
Member

Bug

Fixes:

Description

PR Checklist

  • Meaningful title, helpful description and a linked NuGet/Home issue
  • Added tests
  • Link to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc.

@nkolev92 nkolev92 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some really good learnings there.

Considering having it read the coding guidelines and also an idea would be to separate some of the things that are general coding guidelines out of it, so that all coding agents in general can benefit.

# NuGet/NuGet.Client PR Review Agent

You are an expert code reviewer for the **NuGet/NuGet.Client** repository. You
review pull requests the way the repo's senior maintainers do. Your judgment is distilled

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The newlines are weird.

Probably a good idea to ask it to follow one sentence per line.

PRs #2201–#7492). Optimize for **high signal**: surface real bugs, compatibility
breaks, and design problems; stay silent on noise.

This document is self-contained: **Part 1** is how you operate; **Part 2** is the

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can get out of date, so prefer having it reference the documentation we already have.

As well as coding guideliens too.

- **Category:** Correctness — **Severity:** blocking

### 1.3 Use case-insensitive, culture-correct comparisons for identifiers and paths
- **Why:** Package IDs, framework names, and file paths must compare with `OrdinalIgnoreCase`; culture-sensitive or case-sensitive comparison breaks on Linux/macOS and in non-English cultures.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A lot of these are helpful coding information for our whole repo, both human and agents.

Worthwhile consider putting some of those in a doc so that coding agents can follow them regardless of whether it's a PR review agent or just general coding.

@dotnet-policy-service dotnet-policy-service Bot added the Status:No recent activity PRs that have not had any recent activity and will be closed if the label is not removed label Jul 6, 2026
@Nigusu-Allehu Nigusu-Allehu self-assigned this Jul 6, 2026
@dotnet-policy-service dotnet-policy-service Bot removed the Status:No recent activity PRs that have not had any recent activity and will be closed if the label is not removed label Jul 6, 2026
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.

2 participants