Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

api-change-protocol

Étoiles0

Forks0

Mis à jour30 mars 2026 à 16:44

Review API or route changes for backward compatibility, contract drift, and documentation impact. Trigger when endpoints, handlers, or request/response contracts change.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

njfio

njfio/swarmx

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	api-change-protocol
description	Review API or route changes for backward compatibility, contract drift, and documentation impact. Trigger when endpoints, handlers, or request/response contracts change.
owner	any
trigger	api_changed
version	2

API Change Protocol

Use this when API endpoints, handlers, or request/response contracts change.

Workflow

Identify the contract surface: routes, request fields, response fields, status codes, auth requirements, and error shapes.
Check for breaking changes: removed fields, renamed fields, stricter validation, changed status codes, or changed response structure.
Verify shared types and docs stay aligned: OpenAPI, route docs, client expectations, and shared request/response models.
Prefer additive changes and compatibility shims where possible.
If the change is intentionally breaking, say so explicitly and note the migration impact.

Report

what changed
whether it is safe, caution, or breaking
what docs or client contracts must be updated

This skill is about API contract safety, not about forcing stub-first implementation rituals in every codebase.

Plus depuis ce dépôt

même dépôt

architecture-decision-quality

njfio/swarmx

Turn a specification into a concrete architecture with stable contracts, file boundaries, ownership, and risk analysis. Use this when acting as the architecture writer for a task.

2026-04-030

code-change-verification

njfio/swarmx

Run the project verification stack after code changes. Trigger on code changes and stop on the first failure, fix it, then rerun the full stack from the top.

2026-04-030

new-file-placement

njfio/swarmx

Verify that newly created files follow the repo's existing directory layout, naming conventions, and export patterns. Trigger when a new file is created.

2026-04-030

planning-decomposition-quality

njfio/swarmx

Break architecture into execution-ready sub-tasks with clear ownership, dependencies, and contract references. Use this when acting as the planner for a task.

2026-04-030

playwright-browser-automation

njfio/swarmx

Use Playwright for browser automation, UI validation, E2E tests, and interaction debugging. Useful for flows that need real page navigation, assertions, screenshots, or request interception.

2026-04-030

pre-merge-checklist

njfio/swarmx

Final merge-readiness check after gates pass. Confirms verification is green, changed files are clean, and obvious release blockers are gone before merge.

2026-04-030

name	api-change-protocol
description	Review API or route changes for backward compatibility, contract drift, and documentation impact. Trigger when endpoints, handlers, or request/response contracts change.
owner	any
trigger	api_changed
version	2

API Change Protocol

Use this when API endpoints, handlers, or request/response contracts change.

Workflow

Identify the contract surface: routes, request fields, response fields, status codes, auth requirements, and error shapes.
Check for breaking changes: removed fields, renamed fields, stricter validation, changed status codes, or changed response structure.
Verify shared types and docs stay aligned: OpenAPI, route docs, client expectations, and shared request/response models.
Prefer additive changes and compatibility shims where possible.
If the change is intentionally breaking, say so explicitly and note the migration impact.

Report

what changed
whether it is safe, caution, or breaking
what docs or client contracts must be updated

This skill is about API contract safety, not about forcing stub-first implementation rituals in every codebase.