claude-code-awesomeness

Use this skill when reviewing code, pull requests, or diffs. Prioritizes bugs and security over style.

Use this skill when writing or modifying source files. Controls when JSDoc applies (exported functions and classes), required tags (@param, @returns, @throws), what to skip (private helpers under 10 lines, obvious getters/setters), and inline-comment policy (WHY not WHAT).

Use this skill when creating git commits or drafting commit messages. Enforces conventional-commits format with type, scope, imperative-mood description, 72-char subject limit, and a forbidden-message list ("update", "fix", "WIP", "various improvements", etc.).

Use this skill when writing or modifying Python test files. Enforces pytest as the framework, src-mirroring file paths, test_-prefixed function names, fixtures for shared setup, parametrize for similar cases, and specific-value assertions over truthiness.

Use this skill always, on every code-generation request. Strips Al tells from Claude's output. Forces specific variable names, useful comments only, realistic example data, and concrete code over demonstration code.

Use this skill when writing or modifying test files in this project. Enforces Vitest as the framework, file-path mirroring (src/x.ts → tests/x.test.ts), describe/it structure, three minimum tests per function, and specific-value assertions over truthiness. paths: