$ ~/registry/skill/affaan-m-agents-skills-everything-claude-code

SKILL

everything-claude-code

Helps developers follow this JavaScript repository's coding, testing, and commit conventions.

Stars

★ 244,048

Source

GitHub

Updated

2026-08-29

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 244.0k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "everything-claude-code" skill from askskill:
1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/.agents/skills/everything-claude-code/SKILL.md
2. Save it as ~/.claude/skills/everything-claude-code/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Add a feature following repo conventions

Prompt

Based on everything-claude-code conventions, suggest how to implement a JavaScript feature module: follow the hybrid organization, use relative imports, apply naming conventions, and explain where files should go.

Expected

Recommendations for code structure, naming, import style, and file placement that match the repository conventions.

Write tests that match existing patterns

Prompt

I just added a JavaScript function. Using everything-claude-code testing conventions, suggest the test filename, where it should live, and provide a sample *.test.js skeleton.

Expected

Suggested test naming and placement, plus a sample test structure aligned with existing patterns.

Generate a compliant commit message

Prompt

I updated documentation and fixed a small bug. Generate three concise commit message options using everything-claude-code Conventional Commits rules.

Expected

Concise commit message candidates using prefixes like feat, fix, and docs.

// use cases

Maintain consistency when building new features

When changing the everything-claude-code repository, developers can use this skill to align with the existing module organization, naming style, and import patterns. It is especially useful for JavaScript changes that should match established repository conventions.

Add tests that match repository patterns

When a team needs to add tests for new code, this skill helps mirror the repository's existing test patterns, including separate test locations and the *.test.js naming style. This makes new tests fit the current structure more naturally.

Standardize commit messages

Before committing code, developers can use it to generate or check messages that follow Conventional Commits, such as feat, fix, docs, and test. This helps keep commit history clear and consistent.

// docs

AI summary

The document summarizes the development conventions used in everything-claude-code and explains that this skill helps Claude follow them when working in the repository. It covers the JavaScript tech stack, hybrid module organization, single-package structure, key config files, naming rules, relative import style, test file pattern, and commit message conventions based on Conventional Commits, with examples.

Show full docs ▾

Everything Claude Code Conventions

Generated from 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

feat(rules): add C# language support

Commit message example

chore(deps-dev): bump flatted (#675)

Commit message example

fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691)

Commit message example

docs: add Antigravity setup and usage guide (#552)

Commit message example

merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer

Commit message example

Revert "Add Kiro IDE support (.kiro/) (#548)"

Commit message example

Add Kiro IDE support (.kiro/) (#548)

Commit message example

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

// 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

try {
  const result = await riskyOperation()
  return result
} catch (error) {
  console.error('Operation failed:', error)
  throw new Error('User-friendly message')
}

Common Workflows

These workflows were detected from analyzing commit patterns.

Database Migration

Database schema changes with migration files

Frequency: ~2 times per month

Steps:

Create migration file
Update schema definitions
Generate/update types

Files typically involved:

**/schema.*
migrations/*

Example commit sequence:

feat: implement --with/--without selective install flags (#679)

…

View full docs ↗

// FAQ

What does this skill mainly do?

It teaches Claude to follow the development patterns and conventions used in the everything-claude-code repository. Based on the provided information, it covers JavaScript code style, project structure, testing patterns, and commit message conventions.

When should I use it?

Use it when changing this repository, adding new features, writing tests that match existing patterns, and creating properly formatted commit messages. The documentation explicitly lists these as recommended use cases.

What technical prerequisites does it assume?

The provided information indicates the project primarily uses JavaScript, with a hybrid module organization, relative imports, and mixed exports. No specific test framework was detected, and further details should be checked in the source repository.

Understand your codebase in terminal and accelerate coding with natural language.

codeaashuGet→

MCP

claude-code

Delegate code investigation, edits, and verification to Claude Code with background job management.

—Get→

SKILL

developing-claude-code-plugins

Build, update, test, and release Claude Code plugins efficiently end to end.

obraGet→

SKILL

★640

claude-skills-marketplace

Use Claude skills to automate Git, testing, and code review workflows.

mhattingpeteGet→

$ loading_

// examples

// use cases

// docs

Everything Claude Code Conventions

Overview

Tech Stack

When to Use This Skill

Commit Conventions

Commit Style: Conventional Commits

Prefixes Used

Message Guidelines

Architecture

Project Structure: Single Package

Configuration Files

Guidelines

Code Style

Language: JavaScript

Naming Conventions

Import Style: Relative Imports

Export Style: Mixed Style

Testing

Test Framework

File Pattern: *.test.js

Test Types

Coverage

Error Handling

Error Handling Style: Try-Catch Blocks

Common Workflows

Database Migration

// FAQ

// from the same source

error-handling

carrier-relationship-management

fsharp-testing

quarkus-tdd

fal-ai-media

quarkus-verification

// similar tools

commit-conventions

claude-code-settings

claude-code

claude-code

developing-claude-code-plugins

claude-skills-marketplace

// examples

// use cases

// docs

Everything Claude Code Conventions

Overview

Tech Stack

When to Use This Skill

Commit Conventions

Commit Style: Conventional Commits

Prefixes Used

Message Guidelines

Architecture

Project Structure: Single Package

Configuration Files

Guidelines

Code Style

Language: JavaScript

Naming Conventions

Import Style: Relative Imports

Export Style: Mixed Style

Testing

Test Framework

File Pattern: *.test.js

Test Types

Coverage

Error Handling

Error Handling Style: Try-Catch Blocks

Common Workflows

Database Migration

// FAQ

// from the same source

error-handling

carrier-relationship-management

fsharp-testing

quarkus-tdd

fal-ai-media

File Pattern: `*.test.js`

File Pattern: `*.test.js`