Guide · Agent skill
How to use the ECC Conventions Guide agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The ecc-conventions skill is a reference document that gives an AI agent a summary of the coding conventions used in the ECC repository. It covers the conventional commit format, file and function naming, relative imports, try-catch error handling, and common change workflows. This guide explains what the skill does, how to install it, how to trigger it with plain requests, and what to watch for.
ECC Conventions Guideaffaan-m/ECC · MIT Download the skill Quick start
- 1Download the ZIP. Download the ecc-conventions skill ZIP from this page. The package contains SKILL.md and agents/openai.yaml.
- 2Choose an install location. Pick a personal install in ~/.claude/skills/, a project install in .claude/skills/, or an upload through Settings, then Capabilities, then Skills in the Claude apps.
- 3Unzip the skill. If you use a folder install, unzip the file so the skill folder sits inside the chosen skills directory.
- 4Make a natural request. Ask for a change, a commit message, tests, or a review in plain language. Naming the ecc-conventions skill makes it clearer which guidance you want.
- 5Check the output. Compare the commit message, naming, imports, and tests against the conventions and the existing repository code before you commit.
What the ecc-conventions skill makes the agent do
An agent skill is a set of instructions that an AI agent such as Claude can load when a task matches its description. This skill teaches the agent the development patterns and conventions used in the ECC repository. Its description is: development conventions and patterns for ECC, a JavaScript project with conventional commits.
Once installed, the agent is more likely to write commits, tests, and code that match the existing style of that project. The skill is a reference document generated from analysis of past commits. It does not perform actions on its own; the agent still does the work, using these conventions as guidance.
- Commit messages in conventional commit format, using prefixes such as fix, test, feat, and docs
- Imperative first lines, such as 'Add feature' rather than 'Added feature'
- camelCase for files and functions, PascalCase for classes, SCREAMING_SNAKE_CASE for constants
- Relative imports rather than absolute ones
- Try-catch blocks for error handling
- Test files named *.test.js, with unit and integration tests described as separate types
Install the ecc-conventions skill
The skill is distributed as a ZIP file from this directory page. Download the ZIP, then choose one of the install routes below. The package includes two files: SKILL.md, which holds the conventions, and agents/openai.yaml.
Option A: install for your user account. Unzip the download into ~/.claude/skills/ so that the skill folder sits inside that directory.
Option B: install for a single project. Unzip the download into the project's .claude/skills/ folder so the skill applies only to that repository.
Option C: upload it in the Claude apps. Open Settings, go to Capabilities, then Skills, and upload the skill there.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project
- App install: Settings → Capabilities → Skills
How to trigger the skill with natural requests
You do not need a special command. The skill's guidance says it should be used when making changes to the repository, adding new features that follow established patterns, writing tests that match project conventions, or creating commits with the proper message format. Ask for one of those tasks in ordinary language and the agent can draw on the skill.
To be explicit, you can name the skill in your request, for example asking the agent to use the ecc-conventions skill before it writes the commit message. Naming it is a helpful habit when you want to confirm the agent is following the conventions rather than its defaults.
- Make these changes following the ECC repo conventions.
- Write a commit message for these changes in the ECC conventional format.
- Add tests for this function that match the repo's test patterns.
- Use the ecc-conventions skill to review how I named these files and functions.
Example of a conventional commit message
The skill lists real commit messages from the ECC history as examples. The first line uses a prefix, an optional scope in parentheses, and a short imperative description. The guide recommends keeping the first line concise, with an average length of about 65 characters.
The following example is copied from the skill's commit examples:
feat: add block-no-verify hook for Claude Code and Cursor (#649)What the skill needs, and safety notes
The skill lists no requirements. It does not run scripts and does not use the network. It consists of documentation files only, so there is nothing to execute on your machine when it is loaded.
The skill is specific to the ECC repository. Its own description notes that the conventions come from one repo's history, so they may be wrong for other projects. The file also states that no specific test framework was detected, so it gives only general testing guidance. Check the agent's test setup against your repository rather than relying on the skill for exact commands.
- Requirements: none listed
- Runs scripts: no
- Uses network: no
- Licence: MIT
- Files: SKILL.md and agents/openai.yaml
Tips for getting good results
Give the agent the task and the repository context together, so it can apply the naming and workflow patterns to the right files. Review the commit message and test code it produces against the conventions, since the skill is a summary and not a linter.
If you want to check a contribution rather than write one, ask the agent to compare your changes against the skill's naming and test patterns. The skill's guidance on common workflows, such as feature development and adding a new skill, can help the agent know which files are usually involved.
- Keep the skill folder unchanged if you want the conventions to match the source
- Use the skill in the repository it describes, where its guidance is most accurate
- Confirm test commands yourself, because no specific test framework was detected
What people use it for
- Writing a commit message in ECC's conventional format, such as feat, fix, docs, or test prefixes
- Naming new files and functions in camelCase and classes in PascalCase to match the codebase
- Adding unit or integration tests that follow the repository's *.test.js pattern
- Reviewing a contribution to see whether it follows the project's naming and workflow patterns
Frequently asked questions
How do I install the ecc-conventions skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder for one repository. You can also upload it in the Claude apps under Settings, then Capabilities, then Skills.
Is the ecc-conventions skill free to use?
The skill is licensed under MIT, as stated in its SKILL.md file. Check the license text in the package for the full terms.
What does the ecc-conventions skill require?
The skill lists no requirements. It does not run scripts and does not use the network, so it only adds guidance documents for the agent to read.
Can I use the ecc-conventions skill on projects other than ECC?
It is not recommended. The conventions were generated from the ECC repository's history and may be wrong for other projects. Use it for ECC contributions, and use your own project's conventions elsewhere.
Why isn't the agent running my tests with the skill?
The skill does not run anything itself. It also says no specific test framework was detected, so it offers only general testing guidance. Tell the agent which test command your repository uses, or follow the repository's existing test patterns.
How does this compare with a linter or formatter?
The skill is a reference of conventions, not a tool that checks or changes code. A linter or formatter enforces rules automatically; this skill guides the agent's writing so its output is more likely to match the existing style.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits contributors to the ECC repository who want an AI agent to write commits, tests, and code in the project's style, and maintainers who want a quick style check. If you work on a different project, or need exact test commands and lint rules, pick a skill or guide built for your own codebase instead.
Download the skill