Everything Claude Code
Keep Claude aligned with the everything-claude-code repo’s JavaScript patterns, test layout, and Conventional Commits when you ship changes in that project.
Overview
Everything Claude Code is an agent skill most often used in Build (also Ship) that teaches Claude this repository’s JavaScript patterns, test placement, and Conventional Commit rules.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill everything-claude-codeWhat is this skill?
- Conventional Commits with fix, test, feat, and docs prefixes drawn from 500 analyzed commits
- JavaScript-first conventions with hybrid module organization and separate test location
- Trigger when editing this repo, adding features, writing matching tests, or formatting commits
- Imperative commit subjects with ~65-character first-line guidance
- Implicit invocation allowed via default prompt for repository convention workflows
- four commit prefixes: fix, test, feat, docs
- ~65 character average first-line commit length
Adoption & trust: 2.1k installs on skills.sh; 210k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are changing a specific Claude-ecosystem repo but the agent keeps guessing folder layout, test style, and commit prefixes that do not match maintainer history.
Who is it for?
Solo builders actively developing or maintaining the affaan-m/everything-claude-code repository with an AI coding agent.
Skip if: Greenfield projects unrelated to this repo or teams that use a different commit standard and do not want Conventional Commits.
When should I use this skill?
Making changes to this repository, adding features following established patterns, writing tests that match project conventions, or creating commits with proper message format.
What do I get? / Deliverables
Patches, tests, and commit messages follow the repo’s analyzed conventions so reviews focus on behavior instead of formatting drift.
- Feature or fix patches aligned with repo structure
- Tests placed per project convention
- Conventional Commit messages with correct prefix
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build because the skill encodes how to implement and extend this repository’s hybrid JS layout and feature patterns. Agent-tooling fits skills that teach an agent repo-specific workflows rather than generic app code.
Where it fits
Add a new rules or skills entry without breaking hybrid module layout the README expects.
Ship documentation updates using docs(...) commits that match the repo’s prefix habits.
Author tests in the separate test location instead of colocating files against project habit.
Prepare a release branch where every commit message stays imperative and prefix-consistent for changelog tooling.
How it compares
Use instead of generic “follow best practices” prompts when you need repo-specific procedural knowledge, not a broad linter config.
Common Questions / FAQ
Who is everything-claude-code for?
Indie and solo developers who work inside the everything-claude-code GitHub repository and want their agent to respect its JavaScript and git conventions automatically.
When should I use everything-claude-code?
During Build when adding features or agent tooling in this repo, during Ship when writing commits and tests, and whenever SKILL.md says to activate for repository changes—even small tasks if conventions are not already in your thread context.
Is everything-claude-code safe to install?
It is documentation-style procedural knowledge without built-in shell or network behavior; review the Security Audits panel on this Prism page before trusting any third-party skill in your agent.
SKILL.md
READMESKILL.md - Everything Claude Code
interface: display_name: "Everything Claude Code" short_description: "Repo workflows for everything-claude-code" brand_color: "#0EA5E9" default_prompt: "Use $everything-claude-code to follow this repository's conventions and workflows." policy: allow_implicit_invocation: true --- name: everything-claude-code description: Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits. --- # Everything Claude Code Conventions > Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-03-20 ## Overview This skill teaches Claude the development patterns and conventions used in everything-claude-code. ## Tech Stack - **Primary Language**: JavaScript - **Architecture**: hybrid module organization - **Test Location**: separate ## When to Use This Skill Activate this skill when: - Making changes to this repository - Adding new features following established patterns - Writing tests that match project conventions - Creating commits with proper message format ## Commit Conventions Follow these commit message conventions based on 500 analyzed commits. ### Commit Style: Conventional Commits ### Prefixes Used - `fix` - `test` - `feat` - `docs` ### Message Guidelines - Average message length: ~65 characters - Keep first line concise and descriptive - Use imperative mood ("Add feature" not "Added feature") *Commit message example* ```text feat(rules): add C# language support ``` *Commit message example* ```text chore(deps-dev): bump flatted (#675) ``` *Commit message example* ```text fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691) ``` *Commit message example* ```text docs: add Antigravity setup and usage guide (#552) ``` *Commit message example* ```text merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer ``` *Commit message example* ```text Revert "Add Kiro IDE support (.kiro/) (#548)" ``` *Commit message example* ```text Add Kiro IDE support (.kiro/) (#548) ``` *Commit message example* ```text feat: add block-no-verify hook for Claude Code and Cursor (#649) ``` ## Architecture ### Project Structure: Single Package This project uses **hybrid** module organization. ### Configuration Files - `.github/workflows/ci.yml` - `.github/workflows/maintenance.yml` - `.github/workflows/monthly-metrics.yml` - `.github/workflows/release.yml` - `.github/workflows/reusable-release.yml` - `.github/workflows/reusable-test.yml` - `.github/workflows/reusable-validate.yml` - `.opencode/package.json` - `.opencode/tsconfig.json` - `.prettierrc` - `eslint.config.js` - `package.json` ### Guidelines - This project uses a hybrid organization - Follow existing patterns when adding new code ## Code Style ### Language: JavaScript ### Naming Conventions | Element | Convention | |---------|------------| | Files | camelCase | | Functions | camelCase | | Classes | PascalCase | | Constants | SCREAMING_SNAKE_CASE | ### Import Style: Relative Imports ### Export Style: Mixed Style *Preferred import style* ```typescript // Use relative imports import { Button } from '../components/Button' import { useAuth } from './hooks/useAuth' ``` ## Testing ### Test Framework No specific test framework detected — use the repository's existing test patterns. ### File Pattern: `*.test.js` ### Test Types - **Unit tests**: Test individual functions and components in isolation - **Integration tests**: Test interactions between multiple components/services ### Coverage This project has coverage reporting configured. Aim for 80%+ coverage. ## Error Handling ### Error Handling Style: Try-Catch Blocks *Standard error handling pattern* ```typescript try { const result = await riskyOperation() return result } catch (error) { console.error('Operation failed:', error) throw new Error('User-friendly message') } ``` ##