# Using checklists

# Introduction

In this section we have captured some of the most critical checklists aimed at making it easier following the many rules and best practices

✔️ Link to Jira bug or feature

✔️ 1-2 line description

✔️ make DRAFT PRs across all related repositories

✔️ mark the PRs as draft

✔️ Code can be merged in

✔️ New tests have been written

✔️ Existing tests pass

✔️ Snyk.io scan is passing

✔️ Code is refactored and clean

✔️ Old code that has been changed as part of the code has been cleaned

✔️ The code is free from console.logs, non-essential code comments

✔️ You have tried to review your own "code changes" and made required updates

✔️ Comments are only used very selectively

✔️ Methods only do one thing

✔️ Method names read like documentation

✔️ Complex conditionals are extracted to methods

✔️ DRYness is ensured via traits / mixins or use-cases

✔️ All relevant methods have test coverage

✔️ Code review has been approved by code Owner

✔️ All automated test pass in GitHub

✔️ For new features: Business side has accepted the solution in the staging environment

✔️ Potential security implications of the PR has been checked by a senior member of the engineering team

✔️ Have a role-back plan been identified in case of critical issues are identified

✔️ For customer facing changes, have the customer success team been informed about changes

✔️ For changes with security or data implications for customers, have relevant customers been informed about the change