[FEATURE] Add CONTRIBUTING.md guide for community contributors
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Start by reading the top-level CLAUDE.md and mods/README.md to gather existing guidance, then inspect the mods/, plugins/, examples/ and scripts/ directories. Add a top-level CONTRIBUTING.md covering repository layout, local validation commands, contribution workflow, DevContainer setup, and the Code of Conduct link. Done when the guide provides the requested community starting point and its commands and links are accurate.
Written by the indexing model from the issue text.
Description
Problem Statement
The repository currently lacks a dedicated top-level CONTRIBUTING.md guide. While CLAUDE.md and mods/README.md provide guidance for coding agents and internal mods, community contributors navigating the repository do not have a single standard starting point covering:
- Repository layout and structure (
mods/,plugins/,examples/,scripts/) - How to test changes locally (e.g. running
claude plugin test, typechecking withtsc -p mods/tsconfig.json) - Issue and PR workflow standards
- DevContainer / environment setup
Proposed Solution
Add a top-level CONTRIBUTING.md that:
- Links to the Code of Conduct and welcomes community contributions.
- Describes the directory structure and where to contribute (e.g., mods, examples, docs).
- Outlines local testing, typechecking, and validation commands.
- Explains how to submit bug reports, feature requests, and pull requests.
Priority
Medium - Would be very helpful
Category
Documentation
- Dominant language
- TypeScript
- Stars
- 154k
- Forks
- 25.6k
- Avg merge
- 12h 27m
- Merged PRs (30d)
- 4
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anthropics/claude-code
-
area:plugins bug has repro platform:linux
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anthropics/claude-code#108218 ·
-
area:tui bug keybindings platform:linux
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
anthropics/claude-code#108201 ·
-
area:agents area:plugins bug has repro platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anthropics/claude-code#108157 ·
-
area:api area:docs documentation enhancement platform:macos
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
anthropics/claude-code#108146 ·
-
area:chrome area:permissions bug has repro platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
anthropics/claude-code#108139 ·
All issues in anthropics/claude-code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
earendil-works/pi-claude-code#36 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Resources: New work of jabodetabekPossibly taken @rmt-svc claimed this today. Openresources
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
railmapgen/rmp-gallery#4167 ·
Maintainers usually reply within 2 days
-
documentation p1
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
microsoft/monaco-editor#5577 ·
Maintainers usually reply within 1 day