Add pre-commit hooks

[henilshahdev]

Things to care for:

1. branch names
2. functions & variable names
3. files and folder names
4. react / next / TS basic best practices

[Utkarsh-Singhal-26]

Can you provide more reference on this? Like:

• What branch names are you allowing?
• How should function and variable names be – snake_case, PascalCase, camelCase, or something else?
• Same for folder and file names – what's the convention?
• For the React/Next/TS best practices, any specific patterns or guidelines you think should be followed?

[henilshahdev]

Hey @Utkarsh-Singhal-26, my apologies for the delay.
Here's some details to your questions, let me know if need anything else.

1. Branch Names → feat/*, fix/*, docs/*, refactor/*, chore/* (Lowercase + kebab-case)
2. Functions & Variable Names → camelCase
3. Components / types → PascalCase
4. Constants → UPPER_SNAKE_CASE
5. Files & Folders → kebab-case everywhere

React/Next/TS best practices:

• No any unless unavoidable
• Strictly typed props
• No unused vars/imports
• Keep components small & clean
• Follow Next app router conventions

Maybe we can also follow something from skills