Skip to content

[github] Rename macios-reviewer skill to code-review #26459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rolfbjarne merged 1 commit into from
Sep 2, 2026
Merged

[github] Rename macios-reviewer skill to code-review #26459

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/skills/macios-reviewer/SKILL.md → .github/skills/code-review/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
name: macios-reviewer
name: code-review
description: >-
Review dotnet/macios PRs against established rules. Trigger on "review this PR",
a GitHub PR URL, or code review requests. Checks bindings, MSBuild, nullable,
Expand Down
0 ...acios-reviewer/references/review-rules.md → ...ls/code-review/references/review-rules.md
View file
Open in desktop
File renamed without changes.
4 changes: 2 additions & 2 deletions .github/workflows/macios-reviewer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,8 +72,8 @@ A maintainer commented `/review` on this pull request. Perform a thorough code r

## Instructions

1. Read the review rules from `.github/skills/macios-reviewer/references/review-rules.md` — these contain the detailed patterns and anti-patterns to check for.
2. Read the review methodology from `.github/skills/macios-reviewer/SKILL.md` — this defines the review workflow, mindset, severity levels, and comment format.
1. Read the review rules from `.github/skills/code-review/references/review-rules.md` — these contain the detailed patterns and anti-patterns to check for.
2. Read the review methodology from `.github/skills/code-review/SKILL.md` — this defines the review workflow, mindset, severity levels, and comment format.
3. Follow the skill's workflow to analyze the pull request:
- Gather context: read the diff and changed files
- For each changed file, read the **full source file** to understand surrounding context
Expand Down