docs: finalize quality gate and automated hooks

[niyazmft]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the project's code quality and developer workflow by introducing automated pre-commit hooks. These hooks leverage lint-staged to ensure that all staged code adheres to established linting standards for various file types, automatically applying fixes where possible. Concurrently, the documentation has been updated to guide developers through these new quality gates, and project scripts have been refined for better management of PM2 processes.

Highlights

• Automated Code Quality Gates: Implemented Husky pre-commit hooks and configured lint-staged to automatically fix and validate code (JavaScript, Vue, JSON, CSS, Markdown) before commits, ensuring consistent code quality.
• Updated Developer Documentation: Enhanced GEMINI.md and README.md with new sections detailing the linting and quality process, including instructions for auto-fixing lint errors and mentioning the active pre-commit hook.
• Refined PM2 and Build Scripts: Modified package.json to streamline PM2 commands by adding pm2:stop, pm2:restart, and pm2:logs scripts, while removing the pnpm run build step from pm2:start and deprecating standalone build and preview scripts.
• Dependency Management Updates: Added husky and lint-staged as development dependencies and updated pnpm-lock.yaml to reflect these new packages and their transitive dependencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces pre-commit hooks using Husky and lint-staged to automate code formatting and linting, which is a great step for maintaining code quality. The related documentation in README.md and GEMINI.md has also been updated. However, I've found a critical issue where the build script has been removed from package.json, which will break the production build process. There are also a few inconsistencies between the lint-staged configuration, the npm scripts, and the documentation that should be addressed for clarity and correctness.