Skip to content

🔍 Code Review Process

At Darukaa, we follow a strict code review process to maintain code quality and knowledge sharing across the team.

4-Eye Principle

  • Every Pull Request (PR) must be reviewed and approved by at least one other team member (minimum two sets of eyes).
  • Reviewers should verify:
  • Code correctness & logic
  • Code style & consistency
  • Security and performance considerations
  • Adequate test coverage
  • Documentation updates if needed

PR Best Practices

  • Title & Description
    Provide a clear, concise title and a detailed description explaining:
  • What problem the PR addresses
  • Summary of the changes

  • Any relevant links (issue, design docs, tickets)

  • Labels
    Apply appropriate labels for easier tracking, e.g.:

  • feature
  • bugfix
  • documentation
  • needs review

  • urgent

  • Size & Scope
    Keep PRs small and focused to speed up reviews and reduce merge conflicts.

After Approval

  • Once approved, the PR can be merged by the author or reviewer.
  • Ensure CI checks pass before merging.
  • Delete the branch after merge to keep the repo clean.

Questions?

Reach out in #product-team.

Following this process helps us ship safe, maintainable, and high-quality code — together. 🚀