everything-claude-code-conventions

Applies repository-specific commit, testing, and workflow conventions for JavaScript projects.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/inuishan/PET --skill everything-claude-code-conventions-inuishan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: everything-claude-code-conventions
Source: https://github.com/inuishan/PET/tree/main/.codex/skills/everything-claude-code
Command: npx skills add https://github.com/inuishan/PET --skill everything-claude-code-conventions-inuishan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often struggle to match an unfamiliar repository's established patterns for commits, naming, testing, and workflows, leading to rejected pull requests and inconsistent code. This Skill encodes the conventions of the everything-claude-code repository so changes align with existing standards from the start. ## Core Features & Use Cases - Commit Message Guidance: Enforces conventional commit format (feat:, fix:, docs:, test:) with imperative mood and concise first lines based on 500 analyzed commits. - Code Style Rules: Documents naming conventions (camelCase files and functions, PascalCase classes, SCREAMING_SNAKE_CASE constants), relative import style, and try-catch error handling patterns. - Workflow Templates: Provides step-by-step recipes for common tasks like adding new skills, agents, commands, language rules, and hooks, including typical files involved and example commit sequences. - Use Case: When adding a new skill to the repository, follow the documented workflow: create skills/{skill-name}/SKILL.md, optionally add scripts, and address review feedback per the established template. ## Quick Start Use the everything-claude-code conventions skill to draft a commit message and implementation plan for adding a new language rules directory to this repository.

Frequently Asked Questions about everything-claude-code-conventions

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: with imperative mood and a concise first line around 65 characters. Examples include 'feat(rules): add C# language support' and 'fix: auto-detect ECC root from plugin cache'.

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

Create a directory under skills/{skill-name}/ containing a SKILL.md with sections for When to Use, How It Works, and Examples. Optionally add supporting scripts under skills/{skill-name}/scripts/, then iterate on review feedback.

What naming conventions does this JavaScript project use?▼

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

Does this repository require tests for new features?▼

Yes, the documented feature development workflow includes adding tests alongside implementation and updating documentation. Coverage reporting is configured with a target of 80% or higher.

What are the limitations of auto-generated convention skills?▼

Auto-generated conventions reflect historical commit patterns and may miss unwritten team norms or recent changes. The SKILL.md footer recommends reviewing and customizing the generated content for your team's actual needs.