# Contributing to Microsandbox

Thanks for wanting to help improve microsandbox. This guide is intentionally short: use it for contribution flow, and use [DEVELOPMENT.md](./DEVELOPMENT.md) for local setup, build, test, and release details.

## Need Help?

For development questions, join us on [Discord][discord]. For bugs and feature requests, please use GitHub issues so the discussion stays attached to the work.

## Code of Conduct

Please read and follow our [code of conduct](./CODE_OF_CONDUCT.md). We want microsandbox to stay welcoming, direct, and useful for everyone contributing.

## Ways to Contribute

- Report bugs or request features with a GitHub issue.
- Start broader design or usage conversations in [GitHub discussions][gh-discussions] or [Discord][discord].
- Pick up a [good first issue][good-first-issues] if you want a scoped starting point.
- Improve docs, tests, examples, packaging, platform support, or code.

## Development Setup

Follow [DEVELOPMENT.md](./DEVELOPMENT.md) to install prerequisites, build the project, run tests, and understand the release workflow.

## Pull Requests

1. Fork the repository and create a focused branch.
2. Keep the change scoped to one bug fix, feature, or documentation improvement.
3. Add or update tests and documentation when behavior changes.
4. Use [conventional commits][conventional-commits] for commit messages.
5. Run the relevant checks from [DEVELOPMENT.md](./DEVELOPMENT.md), then open a pull request with a clear summary and test plan.

If you are unsure which checks apply, mention that in the PR. We can help narrow it down.

[conventional-commits]: https://www.conventionalcommits.org/en/v1.0.0/
[discord]: https://discord.gg/T95Y3XnEAK
[gh-discussions]: https://github.com/superradcompany/microsandbox/discussions
[good-first-issues]: https://github.com/superradcompany/microsandbox/labels/good%20first%20issue