Skip to content

Replace .github/prompts with .github/skills for API review#66395

Open
javiercn wants to merge 5 commits intomainfrom
javiercn/api-reviews
Open

Replace .github/prompts with .github/skills for API review#66395
javiercn wants to merge 5 commits intomainfrom
javiercn/api-reviews

Conversation

@javiercn
Copy link
Copy Markdown
Member

Summary

Removes the old .github/prompts/ApiReview.prompt.md file which has been superseded by the .github/skills/api-review/ skill.

The skill provides a richer structure with:

  • SKILL.md with structured frontmatter and workflow
  • references/section-guidelines.md with detailed per-section guidance
  • assets/issue-template.md matching the repo's API proposal template
  • Anti-pattern documentation and quality checklist

Changes

  • Deleted .github/prompts/ApiReview.prompt.md
  • No other changes needed — the skill already exists and is fully functional

javiercn and others added 2 commits April 20, 2026 16:21
Convert the existing ApiReview.prompt.md into a Copilot skill that guides
agents through filling out API review issues following the ASP.NET Core
team's process and template.

The skill is knowledge-driven (no scripts) with:
- SKILL.md: Core workflow, anti-patterns, output contract
- references/section-guidelines.md: Per-section guidance with examples
- assets/issue-template.md: Issue body template

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The api-review prompt has been superseded by the .github/skills/api-review/
skill which provides richer structure with a SKILL.md, section guidelines,
issue template, and reference materials.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 20, 2026 15:20
@javiercn javiercn requested review from a team and wtgodbe as code owners April 20, 2026 15:20
@github-actions github-actions Bot added the needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically label Apr 20, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR transitions API review issue-authoring guidance from the legacy .github/prompts/ApiReview.prompt.md prompt file to a structured .github/skills/api-review/ skill, including a reusable issue body template and per-section guidance.

Changes:

  • Added an api-review skill (SKILL.md) with a defined workflow, prerequisites, quality checklist, and anti-patterns.
  • Added reference documentation for per-section guidance (references/section-guidelines.md) and an API proposal issue body template (assets/issue-template.md).
  • Removed the legacy .github/prompts/ApiReview.prompt.md file.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
.github/skills/api-review/SKILL.md Adds the main skill definition, workflow, quality checklist, and references.
.github/skills/api-review/references/section-guidelines.md Adds detailed guidance and examples for each API proposal section.
.github/skills/api-review/assets/issue-template.md Adds a reusable API proposal issue body template aligned with the repo’s API proposal structure.
.github/prompts/ApiReview.prompt.md Deletes the legacy prompt-based instructions.

Comment on lines +1 to +9
---
name: api-review
description: >
Fill out API review issues for ASP.NET Core following the team's process and template.
USE FOR: writing API review issues, preparing api-ready-for-review proposals, filling
API proposal templates, creating API review descriptions from issues and commits,
"fill out the API review", "prepare API review".
DO NOT USE FOR: reviewing API design decisions, approving APIs, general code review.
---
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

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

PR description says the api-review skill already exists and that no other changes are needed, but this PR is adding the entire .github/skills/api-review/ content (SKILL + references + assets). Please update the PR description to reflect the additional new files, or split the change into separate PRs to avoid confusion during review/history.

Copilot uses AI. Check for mistakes.
Adds a workflow that automatically detects new public APIs in merged PRs
by analyzing PublicAPI.Unshipped.txt changes, checks for existing API
review issues, and creates api-suggestion issues for uncovered APIs.

The workflow:
- Triggers on merged PRs that change PublicAPI.Unshipped.txt files
- Extracts net-new API additions (filtering out signature updates)
- Searches existing api-suggestion/api-ready-for-review/api-approved issues
- Creates grouped API review issues with the standard template
- Adds appropriate area labels based on file paths
- Posts a summary comment on the triggering PR

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework and removed needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically labels Apr 20, 2026
@dotnet-policy-service
Copy link
Copy Markdown
Contributor

Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at.

javiercn and others added 2 commits April 20, 2026 18:38
Instead of duplicating the issue template and section guidelines inline,
the workflow now instructs the agent to read the skill files at runtime:
- .github/skills/api-review/assets/issue-template.md
- .github/skills/api-review/references/section-guidelines.md
- .github/skills/api-review/SKILL.md

This keeps the template in a single source of truth and ensures the
workflow stays in sync with skill updates.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add a pre-activation step that checks github.event.pull_request.merged
and exits early (exit 1) for PRs that were closed without merging.
The workflow agent only runs when merged_check_result == 'success'.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants