Add build perf baseline eval tests#128
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request adds evaluation test scenarios for the build-perf-baseline skill, which helps developers establish build performance baselines and identify optimization opportunities. The PR creates a multi-project .NET solution intentionally designed with build performance issues (redundant project references, unnecessary analyzer settings) for the AI agent to detect and diagnose.
Changes:
- Added a new test scenario
eval.yamlthat instructs the AI to measure cold/warm/no-op builds and identify optimization opportunities - Created a 5-project .NET solution (Common → DataAccess → BusinessLogic → WebApi + Tests) with intentional performance anti-patterns
- Configured Directory.Build.props with performance-impacting settings like
GenerateDocumentationFileandEnforceCodeStyleInBuildalways enabled
Reviewed changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
eval.yaml |
Test scenario definition with assertions for build baseline measurement and optimization recommendations |
PerfBaseline.sln |
VS solution file defining 5 projects with multiple configurations |
PerfBaseline.slnx |
Empty XML-based solution file (issue: should contain project entries or be removed) |
Directory.Build.props |
Shared build properties with intentionally slow settings (doc generation, analyzers always on) |
Common/Common.csproj |
Base library project with entity models and utilities |
Common/Models.cs |
Entity, Result, and StringExtensions implementation |
DataAccess/DataAccess.csproj |
Data access layer depending on Common |
DataAccess/Repository.cs |
Simple in-memory repository implementation |
BusinessLogic/BusinessLogic.csproj |
Business logic layer with intentional redundant Common reference |
BusinessLogic/EntityService.cs |
Service layer wrapping repository operations |
WebApi/WebApi.csproj |
API entry point with intentional redundant transitive references |
WebApi/Program.cs |
Console application demonstrating service usage |
Tests/Tests.csproj |
Test project with intentional redundant references (issue: missing OutputType) |
Tests/EntityServiceTests.cs |
Simple test implementations with Main method |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
Skill Validation Results
Model: claude-opus-4.6 | Judge: claude-opus-4.6 |
ViktorHofer
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.