Thanks for contributing to Extension.js.

• Search existing issues and discussions before opening a new one.
• Use Discussions for questions, early ideas, and product feedback.
• Use Issues for reproducible bugs, focused feature requests, and follow-up work.

• Keep changes focused and easy to review.
• Preserve compatibility when possible. If a change breaks existing behavior, document it clearly.
• Add tests or validation steps when they help verify the change.
• Update the docs when behavior, APIs, or workflows change.

• Explain the problem and why the change is needed.
• Link any related issue or discussion.
• Include a short test plan with the commands or manual steps you ran.
• Keep pull requests focused on one logical change.

If you are not sure where to start, open a discussion first:

• Extension.js discussions
• Extension.js Discord