feat: add rest-api-design-reviewer skill and agent#2201
Open
Andre-D-Rez wants to merge 1 commit into
Open
Conversation
Contributor
🔒 PR Risk Scan ResultsScanned 4 changed file(s).
|
Contributor
🔍 Vally Lint Results
Summary
Full linter output |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new REST API Design Reviewer capability to the awesome-copilot catalog by introducing a skill (procedure/checklist) and a companion agent (persona + execution approach), and registering both in the generated docs indexes.
Changes:
- Added
rest-api-design-reviewerskill with REST audit criteria and OpenAPI 3.1 generation instructions. - Added
REST API Design Revieweragent definition intended to apply the skill’s structured review format. - Updated skills and agents documentation indexes to include the new entries.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| skills/rest-api-design-reviewer/SKILL.md | New skill defining the REST audit checklist and required output format. |
| agents/rest-api-design-reviewer.agent.md | New agent persona/behavior intended to follow the skill’s procedure. |
| docs/README.skills.md | Registers the new skill in the skills index. |
| docs/README.agents.md | Registers the new agent in the agents index. |
| @@ -0,0 +1,156 @@ | |||
| --- | |||
| name: rest-api-design-reviewer | |||
| description: Reviews REST API design, including naming conventions, status codes, and versioning, and automatically generates the OpenAPI spec | |||
| name: "REST API Design Reviewer" | ||
| --- | ||
|
|
||
| You are an expert REST API architect with deep knowledge in RESTful design principles, OpenAPI specifications, and developer experience. Always follow the review procedures defined in `.github/skills/rest-api-design-reviewer/SKILL.md` before responding — that file contains the full checklist, severity labels, output format tables, and OpenAPI template to use. |
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.
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.mainbranch for this pull request.Description
Adds a REST API Design Reviewer skill and agent that audits REST API design quality and generates OpenAPI 3.1 specifications from existing routes and controllers.
The skill activates automatically when the user asks to review, audit, or improve a REST API. It runs a structured check across six categories: naming conventions (plural nouns, no verbs in paths, kebab-case), HTTP method semantics (correct use of GET/POST/PUT/PATCH/DELETE), status code correctness (201 on creation, 204 on delete, 422 on validation errors), versioning strategy (explicit
/api/v1/prefix), response envelope consistency (data/meta structure, standardized error shape), and security concerns (auth headers, sensitive query params, rate limiting documentation). Every finding is classified as [CRITICAL], [WARNING], or [SUGGESTION] with a concrete before/after fix and a one-line explanation of the REST principle violated. The output always closes with a full OpenAPI 3.1 YAML specification and a Richardson Maturity Model score (Levels 0–3).The agent provides a Senior REST API Architect persona. Before responding, it reads the actual route files and controllers in the workspace rather than assuming the API structure. It then follows the skill's review procedures to produce the same structured output: Review Summary table, Findings blocks, OpenAPI 3.1 spec, and Richardson Score, and ends every session with a prioritized action list ordered by severity.
The two work together because the agent handles the behavior (reading files, assuming the architect persona, deciding what to investigate) while the skill defines the procedure (what to check, how to classify findings, what format to output). The agent explicitly references the skill file before responding, so activating the agent automatically brings the full skill checklist into every review session.
Type of Contribution
Additional Notes
The skill and agent work together: the agent references the skill's procedures to ensure consistent structured output across sessions.
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.