check-patterns

What problem does it solve?

This Skill helps a reviewer verify that repository code adheres to the project's documented conventions in docs/CONVENTIONS.md by spot-checking patterns across backend, API, event, and frontend code while remaining read-only.

Core Features & Use Cases

• Error handling checks: Spot-check Go files to see whether errors are wrapped with context (fmt.Errorf with %w) or returned as bare errors.
• Naming and command patterns: Inspect command/*.go filenames and exported types for CreateX/UpdateX/DeleteX handler naming conventions.
• API and OpenAPI validation: Review internal/api/openapi.yaml for plural collection nouns and appropriate HTTP method usage.
• Event factory and frontend checks: Verify event constructors call NewBaseEvent() and that Svelte component filenames use PascalCase.
• Use Case: A tech lead runs this Skill on recent commits to produce PASS/WARN/FAIL outcomes with file-level examples and remediation notes.

Quick Start

Use the check-patterns skill to audit the repository against docs/CONVENTIONS.md and return a PASS/WARN/FAIL report with specific file examples and explanations.