everything-claude-code

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill everything-claude-code-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: everything-claude-code
Source: https://github.com/diazMelgarejo/orama-system/tree/main/.cursor/.agents/skills/everything-claude-code
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill everything-claude-code-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often struggle to match an unfamiliar repository's established conventions for commits, naming, testing, and workflows, leading to rejected pull requests and inconsistent code. This Skill encodes the everything-claude-code repository's patterns so changes align with project standards from the start. ## Core Features & Use Cases - Commit Convention Guidance: Enforces conventional commit format (feat:, fix:, docs:, test:) with concise imperative messages based on 500 analyzed commits. - Code Style Rules: Documents JavaScript naming conventions (camelCase files and functions, PascalCase classes, SCREAMING_SNAKE_CASE constants), relative imports, 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 follow the established feature development workflow: implement the feature, add tests matching the *.test.js pattern, and write a properly formatted conventional commit message. ## Quick Start Ask the assistant to apply the everything-claude-code conventions when making changes, writing tests, or creating commits in this repository.

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 conventional commit prefixes like feat:, fix:, docs:, and test: followed by a concise imperative description around 65 characters. For example, 'feat(rules): add C# language support' follows the project's analyzed commit patterns.

How do I add a new skill to the everything-claude-code repository?

Create a new directory under skills/{skill-name}/ and add a SKILL.md documenting when to use it, how it works, and examples. Optionally add supporting scripts under skills/{skill-name}/scripts/, then address any review feedback.

What naming conventions does this JavaScript project use?

Files and functions use camelCase, classes use PascalCase, and constants use SCREAMING_SNAKE_CASE. The project prefers relative imports and mixed export styles.

Does this repository require tests for new features?

Yes, new features should include tests following the *.test.js file pattern, and the project has coverage reporting configured with an 80% coverage target. Both unit and integration tests are used.

When should I add a command shim versus a skill?

Default to creating the canonical workflow under skills/{skill-name}/SKILL.md first. Only add a commands/{command-name}.md file when legacy slash command compatibility is intentionally required.