Git Collaboration Standards

Language Rule

• Always respond in the same language the user is using. If the user asks in Chinese, respond in Chinese. If in English, respond in English.

Commit Rules

<type>: <short description>

feat:

fix:

refactor:

test:

docs:

chore:

security:

Commit Workflow

1. Run

   git diff

   to review all changes before staging
2. Stage specific files — avoid

   git add .

   to prevent committing

   .env

   or artifacts
3. Write concise commit message describing the why, not the what
4. Never add

   Co-Authored-By

   lines — commit messages should only contain the description
5. Only commit — never

   git push

   unless explicitly requested
6. Never push directly to main/master — always use feature branches

Branch Naming

feat/<name>

feat/staking-pool

fix/<name>

fix/reentrancy-guard

refactor/<name>

refactor/token-structure

PR Requirements

forge test

forge test --gas-report

Code Review Rules

forge test

AI Assistance Rules

• AI-generated code must pass

  forge test

  before committing
• Always review AI output for: correct import paths, proper access control, gas implications
• Include relevant file paths and test cases in AI prompts for better results
• Run

  forge fmt

  after AI generates code to ensure consistent formatting