conventional-commitslisted

# Conventional Commits ## Workflow 1. Inspect `git status`, staged and unstaged diffs, and recent commit style. 2. Do not stage unrelated files. Never include secrets, generated output, dependencies, local data, or user changes unrelated to the requested work. 3. Run the verification appropriate to the changed files before committing. 4. Choose one commit type and an optional concise scope. 5. Write the subject and body in Chinese unless the repository explicitly uses another language. 6. Run `git diff --cached --check` and review `git diff --cached --stat` before committing. 7. Create the commit non-interactively and report its hash and verification result. ## Message Format Use exactly this structure when the change needs a body: ```text type(scope): 简短中文摘要 - 具体变更一 - 具体变更二 - 具体变更三 - ... - 具体变更n ``` Keep the subject imperative, specific, and free of a trailing period. Separate the body from the subject with one blank line. Use `- ` bullets that describe delivered behavior or artifacts, not the development process. For a genuinely small change, a subject-only commit is acceptable: ```text fix(auth): 修复过期令牌未被拒绝的问题 ``` ## Types - `feat`: Add user-visible behavior. - `fix`: Correct faulty behavior. - `docs`: Change documentation only. - `refactor`: Restructure code without changing behavior. - `test`: Add or revise tests only. - `build`: Change build tools or dependencies. - `ci`: Change automation workflows. - `perf`: Improve performance. - `style`: Change formatting