We love your input! We want to make contributing to ReviewScope as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We use GitHub to host code, to track issues and feature requests, and to accept pull requests.
Please do not start work or open a Pull Request unless an issue or task has been explicitly assigned to you.
This helps avoid duplicate work and keeps the project aligned with current priorities.
If you want to work on something:
- Open an issue first or
- Ask for an existing issue to be assigned to you
- Fork the repo and create your branch from
main. - Install dependencies:
npm install
- Set up environment variables:
- Copy
.env.exampleto.envin the root and relevant app directories (apps/api,apps/worker,apps/dashboard). - Fill in the required keys (see
README.mdfor details).
- Copy
- Run the development environment:
This will start all services (API, Worker, Dashboard) concurrently.
npm run dev
- TypeScript: We use TypeScript for type safety. Please ensure all new code is typed.
- Formatting: We use Prettier for code formatting. Run
npm run formatbefore committing. - Linting: We use ESLint. Run
npm run lintto check for issues. - Commit Messages: Write clear, descriptive commit messages.
apps/: Contains the deployable applications (API, Dashboard, Worker).packages/: Contains shared libraries and internal packages (Context Engine, LLM Core, Rules Engine, Security).
Report bugs using Github's issue tracker
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
By contributing, you agree that your contributions will be licensed under its MIT License.