everything-claude-code

Applies repository conventions for commits, testing, and workflows in JavaScript projects.

Updated May 7, 2026
One-click install
npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill everything-claude-code-mirzadham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: everything-claude-code
Source: https://github.com/mirzadham/trainingroombookingsystem2/tree/main/.agent/.agents/skills/everything-claude-code
Command: npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill everything-claude-code-mirzadham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often struggle to match a repository's established conventions for commit messages, code style, testing patterns, and common workflows, leading to inconsistent pull requests and repeated review cycles. ## Core Features & Use Cases - Commit Convention Guidance: Enforces conventional commit format (feat:, fix:, docs:, test:) with imperative mood and concise messages based on analysis of 500 real commits. - Code Style Standards: Documents naming conventions (camelCase files, PascalCase classes, SCREAMING_SNAKE_CASE constants), relative import style, and try-catch error handling patterns. - Workflow Templates: Provides step-by-step procedures for common tasks like adding new skills, agents, language rules, hooks, and syncing catalog counts. - Use Case: When adding a new feature to the repository, activate this skill to automatically follow the established pattern of implementing the feature, adding matching *.test.js tests, and writing a properly formatted conventional commit message. ## Quick Start Use the everything-claude-code conventions to implement this feature and write a properly formatted commit message.

Frequently Asked Questions about everything-claude-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write conventional commit messages for this repository?▼

Use prefixes like feat:, fix:, docs:, or test: followed by a concise imperative-mood description around 65 characters. For example, 'feat(rules): add C# language support' follows the analyzed commit patterns.

What naming conventions should I follow for JavaScript files?▼

Files and functions use camelCase, classes use PascalCase, and constants use SCREAMING_SNAKE_CASE. Imports should be relative, and test files follow the *.test.js naming pattern.

How do I add a new skill to this repository?▼

Create a directory under skills/{skill-name}/, add a SKILL.md documenting when to use it, how it works, and examples, optionally include scripts, then address review feedback. The same applies to cross-harness copies under .agents/skills/ or .cursor/skills/.

Does this repository require tests for new features?▼

Yes, new features should include tests following the *.test.js file pattern, covering both unit and integration scenarios. The project has coverage reporting configured with a target of 80% or higher.

What error handling pattern does this project use?▼

The project uses try-catch blocks that log the original error and rethrow a user-friendly message. This standard pattern applies to async operations throughout the codebase.