feat: kzb-72 enhance code

[oneanupam]

Description

Please include a short summary of the update made along with the context.

Checklist

• Self-review of the code is performed.
• Code has been fully tested and completely functional.

Type of Change

• break: Resolved a breaking change. This will increment the major version.
• feat: A new feature or enhancement added to the codebase. This will increment the minor version.
• fix: A bug fix or correction to resolve an issue. This will increment the patch version.
• refactor: A code change that doesn’t fix a bug or add a feature but improves code structure. (e.g., folder restructure, function rename). No version increment.
• chore: Changes to the build system (if not using ci: or build: commit pattern), tooling, CI configs, or other non-production code that don’t affect functionality. (e.g., adding .gitignore, linting config or anything realted to infra/config/tooling files (not code)). No version bump.
• docs: Documentation or markdown file changes, not directly affecting the code (e.g., readme and .md files). No version bump.
• ci: Changes to CI/CD configuration files and pipelines (e.g., GitHub Actions, GitLab CI, Jenkins)
• build: Changes related to the build system or project dependencies that affect how the application is built or packaged. (e.g., Modify build.gradle, Makefile, Dockerfile, pom.xml). No version bump.

Reference

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository