x-review-gateway
Reviews API gateway configuration for routing rules, authentication, rate limiting, CORS, security headers, TLS, and observability integration.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- x-review-gateway
- description
- Reviews API gateway configuration for routing rules, authentication, rate limiting, CORS, security headers, TLS, and observability integration.
- allowed-tools
- Read, Grep, Glob, Bash
- argument-hint
- [gateway config files or PR]
- user-invocable
- true
- requires-capabilities
- []
02 资源文件 1
- 参考文档README.md1.4 KB
03 SKILL.md 正文
Global Output Policy
- Language: English ONLY.
- Tone: Technical, Direct, and Concise.
- Efficiency: Remove all conversational fillers and greetings to save tokens.
Skill: API Gateway Review
Purpose
Review API gateway configuration against best practices for routing rules, authentication, rate limiting, CORS, security headers, TLS configuration, and observability integration.
Activation Condition
Include this skill when the project uses an API gateway (Kong, Istio, AWS APIGW, Traefik, etc.).
Triggers
/x-review-gateway-- review all gateway configuration files/x-review-gateway gateway.yaml-- review a specific config file/x-review-gateway 42-- review gateway changes in PR #42
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
target |
String | No | (all) | Gateway config file paths or PR number |
Workflow
Step 1 — Identify Gateway Configuration
Scan for gateway configuration files in the change set or project.
Step 2 — Verify Routing Rules
Check route definitions for correctness, path conflicts, and upstream targets.
Step 3 — Validate Authentication
Verify authentication middleware is applied to protected routes.
Step 4 — Check Rate Limiting
Validate rate limiting configuration per route or globally.
Step 5 — Validate CORS and Security Headers
Check CORS policy and security headers (HSTS, CSP, X-Frame-Options, etc.).
Step 6 — Validate TLS Configuration
Verify TLS settings: minimum version, cipher suites, certificate management.
Step 7 — Check Observability Integration
Validate access logs, tracing propagation, and metrics collection.
Step 8 — Generate Report
Produce gateway review report with findings and verdict.
Output Format
## Gateway Review — [Change Description]
### Gateway Type: [Kong/Istio/AWS APIGW/Traefik]
### Findings
1. [Finding with file, line, remediation]
### Verdict: APPROVE / REQUEST CHANGES
Error Handling
| Scenario | Action |
|---|---|
| No gateway config files found | Report INFO: no gateway configuration discovered |
| Unknown gateway type | Warn and apply generic best practices review |
| Missing authentication on public routes | REQUEST CHANGES with remediation guidance |
04 同仓库更多 Skills
x-parallel-eval
Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan / x-story-plan, applies the parallelism-heuristics knowledge pack (hard / regen / soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.
parallelism-heuristics
Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard / regen / soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.
x-watch-pr-ci
Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.
x-validate-docs
Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared/auto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.
x-update-system-architecture
Incrementally updates docs/architecture/system.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component/integration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.
x-update-architecture
Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.