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".

Ir para a instalação

Repositório: safe-global/safe-client-gateway
Última atividade na origem: 20 de agosto de 2026 às 11:45
Idioma detectado do SKILL.md: inglês
Estrelas: 50
Forks: 102

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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".

2026-08-21

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 todas deste repositório

name

cgw-commits-and-prs

description

CGW Commits and Pull Requests

Read docs/agents/commits-and-prs.md before writing the message. This skill is a loader; the doc is the content.

The load-bearing fact: main is squash-merged, so the PR title becomes the commit subject on main with (#NNNN) appended by GitHub. Branch commit subjects are working notes; the PR title is permanent history.

Shape: <type>(<scope>)?: <description> — lowercase type from the doc's nine, optional scope that is a real src/modules/ directory name in kebab-case, imperative lowercase description, under 72 chars, no trailing period.

Nothing here is machine-enforced. There is no commit-msg hook and no PR-title CI job — .husky/pre-commit only runs env:validate:silent, lint, and format. Every malformed subject on main today got there through that gap, so the check is yours.

PR body: ## Summary and ## Changes — the template's two sections, nothing more. Other guides require their justification in the PR description text itself, not a commit message or a chat thread; those all go in ## Summary, and the doc's PR-body rule names which guides set one. Pre-commit evidence is the PR's own CI run.

Before committing, run the pre-commit checklist from AGENTS.md: yarn format, yarn lint --fix, yarn test.

cgw-commits-and-prs

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

CGW Commits and Pull Requests

CGW Commits and Pull Requests