everything-claude-code-conventions

Codifies commit, code, and workflow patterns for the everything-claude-code JavaScript repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of inconsistent contributions to the everything-claude-code JavaScript repository, where new contributors often unknowingly violate established commit formats, code style rules, and workflow patterns that lead to repeated PR review feedback.

Core Features & Use Cases

  • Conventional Commit Enforcement: Provides clear rules for commit prefixes (feat, fix, docs, test), message length, and imperative mood to match the project's analyzed commit history.
  • Code Style & Architecture Alignment: Defines JavaScript naming conventions, import/export patterns, and the project's hybrid module organization to ensure new code integrates seamlessly with existing codebases.
  • Workflow Standardization: Outlines step-by-step processes for common project tasks including feature development, adding language rules, adding new skills/agents, and syncing catalog counts to reduce review cycles.
  • Use Case: When submitting a PR to add a new feature to the everything-claude-code repo, use this Skill to verify your commit messages, code style, and test coverage meet the project's requirements before opening the pull request.

Quick Start

Use the everything-claude-code-conventions skill to format your next commit to the everything-claude-code repository according to the project's conventional commit rules and code style guidelines.

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 format conventional commits for a JavaScript repository?

Conventional commits for a JavaScript repository require specific prefixes like feat, fix, docs, or test, written in the imperative mood and adhering to message length limits to ensure commit history consistency and streamlined pull request reviews.

What code style conventions should I follow for JavaScript contribution guidelines?

JavaScript contribution guidelines dictate using camelCase naming conventions and aligning with hybrid module organization for imports and exports. Following these code style rules ensures new code integrates seamlessly with the existing project architecture.

How do I standardize testing patterns when adding new features to a project?

To standardize testing patterns when adding new features, implement standardized testing pattern protocols that match the project's existing test coverage requirements. This verifies code quality and reduces repeated PR review feedback before opening a pull request.

Does this conventions skill apply to adding new agents and language rules?

Yes, this conventions skill applies to adding new agents, language rules, and skills by outlining step-by-step workflow standardization processes. It defines exactly how to sync catalog counts and integrate new project components without violating established patterns.

Why do my pull requests get repeated review feedback on repo workflows?

Pull requests get repeated review feedback on repo workflows because new contributors often unknowingly violate established commit formats and code style rules. Enforcing consistent development standards eliminates this friction by codifying observed commit and workflow patterns.