From: Marvin Schenkel <marvinschenkel@gmail.com>
Date: Thu, 26 Feb 2026 11:22:00 +0000 (+0100)
Subject: Try with inline content.
X-Git-Url: https://git.kitaultman.com/?a=commitdiff_plain;h=5e107fdcc0a56cec2723e3650e8becab971cfb98;p=music-assistant-server.git

Try with inline content.
---

diff --git a/.github/instructions/REVIEW.instructions.md b/.github/instructions/REVIEW.instructions.md
index 88c4e27d..5b288df8 100644
--- a/.github/instructions/REVIEW.instructions.md
+++ b/.github/instructions/REVIEW.instructions.md
@@ -5,8 +5,29 @@ excludeAgent: "code-agent" # Only used by the code review agent in Github
 
 # PR Review Standards
 
-When reviewing a pull request, apply the standards defined in:
-https://raw.githubusercontent.com/music-assistant/server/refs/heads/dev/.claude/skills/review-pr/REVIEW_STANDARDS.md
+## What to Analyze
+
+Review all code changes for:
+- Code quality and style consistency with the existing codebase
+- Potential bugs or issues
+- Performance implications
+- Security concerns
+- Test coverage
+- Documentation updates if needed
+
+## PR Title
+
+The PR title must be a functional description of the change. It must NOT contain conventional commit prefixes such as `feat:`, `fix:`, `refactor:`, `chore:`, etc. Labels are used to categorize PRs, not the title. Flag as `[PROBLEM]` if the title uses such prefixes.
+
+## Existing Review Comments
+
+Ensure any existing review comments on the PR have been addressed before approving.
+
+## Issue Categories
+
+Categorize every issue found as one of:
+- `[CRITICAL]` — must be fixed before merging (bugs, security issues, broken functionality)
+- `[PROBLEM]` — should be fixed (code quality, bad patterns, missing tests)
 
 ## Output