### Rules
* title is lowercase, no period at the end.
* Title should be a clear summary, max 50 Chinese characters.
* Use the body (optional) to explain *why*, not just *what*.
* Bullet points should be concise and high-level.
Avoid
* Vague titles like: "update", "fix stuff"
* Overly long or unfocused titles
* Excessive detail in bullet points
### Allowed Types
| Type | Description |
| -------- | ------------------------------------- |
| feat | New feature |
| fix | Bug fix |
| chore | Maintenance (e.g., tooling, deps) |
| docs | Documentation changes |
| refactor | Code restructure (no behavior change) |
| test | Adding or refactoring tests |
| style | Code formatting (no logic change) |
| perf | Performance improvements |
## Rules
* title is lowercase, no period at the end.
* Title should be a clear summary, max 50 Chinese characters.
* Use the body (optional) to explain *why*, not just *what*.
* Bullet points should be concise and high-level.
Avoid
* Vague titles like: "update", "fix stuff"
* Overly long or unfocused titles
* Excessive detail in bullet points
## Allowed Types
| Type | Description |
| -------- | ------------------------------------- |
| feat | New feature |
| fix | Bug fix |
| chore | Maintenance (e.g., tooling, deps) |
| docs | Documentation changes |
| refactor | Code restructure (no behavior change) |
| test | Adding or refactoring tests |
| style | Code formatting (no logic change) |
| perf | Performance improvements |