cgw-review

THE entry point for reviewing a diff or PR in safe-client-gateway, and for verifying your own completed work before committing or opening a PR - load this one first and let it pull in cgw-remarks as its catalog. Covers the repo's two-part review standard - Part 1 maps the diff to the applicable guides via the AGENTS.md routing table and verifies every rule with file:line citations; Part 2 is deviation control (spec match, no scope creep, no new structural deviations, no stale guides - which includes unjustified ratchet-baseline growth, no dead code, pre-commit evidence not assertion, SPDX headers) - plus the required findings format. Triggers on "review this", "look at my diff", "ready to commit", "before PR", "before I open the PR", "definition of done", "is this done", "check my work", "self-review".

Ir a la instalación

Repositorio: safe-global/safe-client-gateway
Última actividad en el origen: 21 de agosto de 2026 a las 09:28
Idioma detectado de SKILL.md: inglés
Estrellas: 50
Forks: 102

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/safe-global/safe-client-gateway --skill cgw-review

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

cgw-commits-and-prs

Use when writing a commit message, a PR title, or a PR body in safe-client-gateway, or when deciding whether a change is too large for one PR. Covers the Conventional Commits shape this repo uses, the nine allowed types and when each applies, module-name scopes, the fact that main is squash-merged so the PR title becomes the permanent commit subject, the required PR body sections (Summary, Changes), how to split an oversized change, and issue linking. Triggers on "commit message", "commit this", "PR title", "PR description", "open a PR", "split this PR", "is this too big".

2026-08-20

cgw-api-dtos

Use when adding or changing an endpoint, a controller handler, a request or response DTO, a Zod schema, Swagger/OpenAPI annotations, or pagination in safe-client-gateway. Covers the ValidationPipe(ZodSchema)-on-every-input rule, the DTO pairing (Zod schema plus an @ApiProperty class declared implements z.infer), the Raw<T> boundary and where Schema.parse() must happen, the four-representations checklist for any persisted-shape field change, pagination via buildPageSchema plus a concrete Page<T> subclass, URI versioning, and the one-error-funnel-per-layer rule. Triggers on "new endpoint", "new route", "add a field", "add a column that clients can see", "return X from the API", "let a user do X" (any new handler), "DTO", "Zod schema", "validation", "Swagger", "OpenAPI", "@ApiProperty", "pagination", "response shape", and on any error-handling question whose subject is which exception type a layer should throw ("what should this datasource throw", "empty catch in a repository", "wrong status code") - the one-err

2026-08-07

cgw-architecture

The system map for safe-client-gateway - load it whenever a change spans more than one layer, or when you need to know what happens between the request arriving and the upstream call. Covers the request lifecycle (Fastify to guards to ValidationPipe to controller to route service to repository to datasource to CacheFirstDataSource to upstream), the layer boundaries and which layer may call which, where Schema.parse() happens, the cache-invalidation flow, the error-funnel map, and the SIWE/JWT/OIDC auth flows. Triggers on "where does this go", "which layer", "how does a request flow", "what calls what", "should this be in the service or the repository", "why is this endpoint slow" (before profiling - the layer map tells you what it touches), "trace this request", "add a feature that needs a new endpoint and a new upstream call", plus any first look at an unfamiliar part of this codebase.

2026-08-07

Ver todos los de este repositorio

CGW Review Checklist

Read docs/agents/reviewing.md and apply both parts. This skill is a loader; the doc is the content.

When a review happens is your process's decision (Superpowers, spec-kit, CI). What to verify in this repo is that doc.

Part 1 — guideline compliance. Map the diff against every row of the AGENTS.md routing table, not just the first match; name the applicable guides in the output; verify every rule each one lists; cite violations as file:line plus the guide's own heading for that rule. "No guide applies" is a valid, statable outcome — a stretched match produces noise.

Part 2 — deviation control. Seven independent checks; passing one never excuses failing another. The two that fail most often: pre-commit evidence (yarn format, yarn lint --fix, yarn test output or a CI link — an unproven "tests pass" is a finding), and SPDX headers on every file the change touched, not just created.

Findings are most-severe-first, as a numbered list — one item each,

N. **[<rule name>](<link to the rule>)** — [<path>:<line>](<permalink>) — <one-sentence defect>. **Fix:** <the concrete change>.

Rule name and location are links, the fix gives the compliant value verbatim, and no report contains a bare #<number> (GitHub autolinks it to an unrelated PR). A clean review states "no findings" explicitly. Full shape: reviewing.md's "Reporting format".

Load cgw-remarks alongside this one — it is the catalog of what this repo's reviewers actually flag, indexed by the shape it takes in a diff.

CGW Review Checklist

Read docs/agents/reviewing.md and apply both parts. This skill is a loader; the doc is the content.

When a review happens is your process's decision (Superpowers, spec-kit, CI). What to verify in this repo is that doc.

Findings are most-severe-first, as a numbered list — one item each,

N. **[<rule name>](<link to the rule>)** — [<path>:<line>](<permalink>) — <one-sentence defect>. **Fix:** <the concrete change>.

Load cgw-remarks alongside this one — it is the catalog of what this repo's reviewers actually flag, indexed by the shape it takes in a diff.

cgw-review

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

CGW Review Checklist

Más de este repositorio

CGW Review Checklist