Check repository code against documented conventions and produce PASS/WARN/FAIL findings.
npx skills add https://github.com/cacack/my-family --skill check-patterns
Please help me install this Agent Skill. Skill: check-patterns Source: https://github.com/cacack/my-family/tree/main/.claude/skills/check-patterns Command: npx skills add https://github.com/cacack/my-family --skill check-patterns
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.
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.
High-intent search queries and answers about installing and using this skill.
To verify code follows established conventions, spot-check recent Go and Svelte files against docs/CONVENTIONS.md, evaluating error wrapping, naming patterns, and component filenames to produce PASS/WARN/FAIL findings with file examples.
Checking OpenAPI specs involves reviewing internal/api/openapi.yaml to ensure plural collection nouns and appropriate HTTP method usage, validating the API design against documented conventions and returning specific rationale for any deviations found.
You can audit Go error handling patterns by spot-checking Go files to determine whether errors are wrapped with context using fmt.Errorf with %w or returned as bare errors, generating a report with concrete file examples.
Convention checking does not require write access; it operates with read-only access to repository files and docs/CONVENTIONS.md, sampling recent files to safely produce PASS/WARN/FAIL outcomes without modifying code.
The best way to check Svelte component naming and event factory usage is to verify Svelte filenames use PascalCase and ensure event constructors call NewBaseEvent(), returning findings with specific file examples and remediation notes.
Code reviews miss CreateX UpdateX DeleteX handler naming conventions when command/*.go filenames and exported types are not spot-checked against docs/CONVENTIONS.md, which this process addresses by sampling recent files and reporting deviations.
cacackDetect documentation drift between project docs and repository code.
jlawsAudit .agents assets for naming, structure, and cross-reference integrity.
emvnuelDesign consistent REST APIs with noun-based endpoints and MicroProfile OpenAPI annotations.
CygnusfearAudit filenames and naming conventions against CLAUDE.md standards.
