everything-claude-code

Conventional commits for JavaScript feature work require concise, imperative messages that categorize changes as features, fixes, docs, or tests. This standardizes commit formatting across the repository to clarify project history.

JavaScript test files must follow the *.test.js naming convention to ensure they are recognized by the repository's testing workflow. This pattern maintains consistent test coverage and organization across the codebase.

Relative imports are required to maintain the hybrid JavaScript module organization within the repository. This convention prevents module resolution failures and ensures consistent dependency mapping across feature work.

The best way to structure error handling is to wrap operations in try-catch blocks. This pattern aligns with the repository's established code quality conventions and prevents unhandled exceptions during feature execution.

Yes, this skill applies to documentation updates and repository synchronization. It provides workflow patterns for adding skills, agents, and hooks while keeping documented counts synchronized with the codebase.