check-patterns

스타2

포크1

업데이트2026년 2월 28일 22:17

Check code follows established patterns from CONVENTIONS.md

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

cacack

cacack/my-family

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Checks

Error handling: Sample 3 recent Go files - do they wrap errors with context (fmt.Errorf with %w) or just return bare errors?
Naming conventions: Are command handlers following the CreateX/UpdateX/DeleteX pattern? Check command/*.go filenames and exported types.
API patterns: Does the OpenAPI spec (internal/api/openapi.yaml) use plural nouns for collections and standard HTTP methods?
Event factory pattern: Do event constructors use NewBaseEvent()? Spot-check 2-3 event types in domain/.
Frontend patterns: Are Svelte components using PascalCase names? Check web/src/lib/components/*.svelte filenames.

Output Format

Report each as PASS/WARN/FAIL with specifics.

이 저장소의 다른 Skills

같은 저장소

audit-architect

cacack/my-family

Architecture audit — layer separation, ES consistency, dependency direction, branching readiness

2026-02-282

audit-docs

cacack/my-family

Audit project documentation for drift against actual code structure

2026-02-282

audit-domain

cacack/my-family

Domain audit — GPS compliance, person/relationship modeling, GEDCOM fidelity

2026-02-282

audit-frontend

cacack/my-family

Frontend audit — component architecture, accessibility, D3 visualization, search UX

2026-02-282

audit-full

cacack/my-family

Full audit — launches all 6 audit skills in parallel, produces unified report

2026-02-282

audit-go

cacack/my-family

Go idioms audit — error handling, concurrency, package design, interfaces, performance

2026-02-282

name	check-patterns
description	Check code follows established patterns from CONVENTIONS.md
context	fork
agent	Explore

You are a Tech Lead checking that code follows established patterns from docs/CONVENTIONS.md. This is READ-ONLY, do not modify files.

Checks

Error handling: Sample 3 recent Go files - do they wrap errors with context (fmt.Errorf with %w) or just return bare errors?
Naming conventions: Are command handlers following the CreateX/UpdateX/DeleteX pattern? Check command/*.go filenames and exported types.
API patterns: Does the OpenAPI spec (internal/api/openapi.yaml) use plural nouns for collections and standard HTTP methods?
Event factory pattern: Do event constructors use NewBaseEvent()? Spot-check 2-3 event types in domain/.
Frontend patterns: Are Svelte components using PascalCase names? Check web/src/lib/components/*.svelte filenames.

Output Format

Report each as PASS/WARN/FAIL with specifics.