Skip to main content
This guide covers how to contribute to the Soundcheck project.

Getting Started

1

Fork the repository

Create a fork of the repository on GitHub.
2

Clone your fork

3

Set up upstream

4

Install dependencies


Branching Strategy

Branch Naming

Branch Flow


Development Workflow

1

Create a feature branch

2

Make your changes

Write code following the project conventions.
3

Run quality checks

4

Commit your changes

5

Push and create PR

Open a pull request targeting dev.

Commit Messages

Follow Conventional Commits:

Examples


Code Style

TypeScript

  • Strong typing required (avoid any)
  • Use interfaces for object shapes
  • Use types for unions and utilities

React

  • Functional components with hooks
  • Memoize expensive computations
  • Keep components focused and small

Imports

Group imports in order:

Pre-Commit Hooks

Husky runs automatically on git commit:
  • TypeScript type checking
  • oxlint on staged files
  • oxfmt on staged files
  • Whitespace error detection
  • TypeScript checks on staged files (mobile, web, api-events, mcp-ts, …)
To bypass in emergencies:

Pull Request Guidelines

PR Title

  • Use conventional commit format
  • Keep under 72 characters
  • Be descriptive

PR Description

Include:
  • What changes were made
  • Why the changes were made
  • How to test the changes
  • Screenshots for UI changes

Review Process

  1. Open PR targeting dev
  2. Wait for CI checks to pass
  3. Request review from team members
  4. Address feedback
  5. Merge when approved

Testing

Mobile

Web

API (api-events)

MCP server (mcp-ts)


Documentation

  • Update docs when adding features
  • Keep README files current
  • Add JSDoc comments for complex functions

Need Help?

  • Create an issue for bugs or questions
  • Check existing issues before creating new ones
  • Join team discussions for architectural decisions