Reason/Context
Why we need this improvement?
We need to enforce code quality standards consistently across the project to maintain readability, maintainability, and consistency. This ensures that our codebase remains clean and free of errors.

How will this change help?
This change will automate the process of checking code quality during the CI (Continuous Integration) pipeline. It will catch potential issues early in the development process, reducing the chances of bugs slipping into production.

What is the motivation?
The motivation behind this improvement is to streamline the development workflow and improve overall code quality. By integrating linting, formatting, and type-checking into our CI pipeline, we can enforce coding standards and catch errors before they impact users.

Description
What changes have to be introduced?
We need to set up tools such as ESLint, Prettier, and TypeScript in our CI pipeline. These tools will be configured to perform linting, code formatting, and type-checking automatically on every code change. Already setup this in my previous issue.

How could it be implemented/designed?
Implementation involves adding appropriate scripts and configurations to our CI setup. We will configure our CI workflow to run commands for linting, formatting, and type-checking on every pull request or code push. Additionally, we may need to update our documentation to inform contributors about these CI checks and how to resolve any issues that arise.

I would love to work on it