菜单
Use when about to open a PR or write a branch summary — generates a structured PR description from the git diff between the current branch and develop.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pre-description |
| description | Use when about to open a PR or write a branch summary — generates a structured PR description from the git diff between the current branch and develop. |
| allowed-tools | Bash, Read |
| model | sonnet |
Generates a Trovara-specific PR description from git history. Run before pr-prep if you only need the description without the full quality-gate pass.
git log develop..HEAD --oneline --no-merges
git diff develop..HEAD --stat
git diff develop..HEAD --name-only
If the diff touches lib/views/ → read lib/views/CLAUDE.md.
If it touches lib/core/services/ai/ → read lib/core/services/ai/CLAUDE.md.
## What
- [User-visible change 1]
- [User-visible change 2]
## Why
[The motivation — a bug report, a spec requirement, a product decision]
## How
- [Key implementation choice — e.g., "Uses SHA-256 signatures in EmbeddingService to skip unchanged note chunks"]
- [Non-obvious architectural decision — e.g., "RagService now streams tokens via a Dart Stream<String> instead of buffering the full response"]
## Test Plan
- [ ] `flutter analyze` — clean
- [ ] `flutter test patrol_test` — passing
- [ ] Manually tested: [golden-path scenario]
- [ ] Edge cases: [list if applicable]
## Notes for Reviewer
[Files that deserve extra attention, known limitations, follow-up tickets]
---
🤖 Generated with [Claude Code](https://claude.ai/code)
| Commit prefix | "What" bullet language |
|---|---|
feat(notes) | New notes capability |
feat(ui) | UI / gesture update |
feat(chat) | AI chat improvement |
feat(sync) | Sync / backup update |
fix(*) | Bug fix — group minor fixes into one bullet |
refactor(*) | Internal cleanup — omit from "What", include in "How" |
chore(deps) | Omit entirely unless the bump fixes a user-facing bug |
perf(*) | Performance improvement |
develop..HEAD).Use when inserting a new i18n key into Trovara's locale files — adds the key to both en.json and km.json under the correct nested path and verifies parity.
Use when incrementing the Trovara app version before a release — updates the semver and build number in pubspec.yaml following the project's versioning convention.
Use when reviewing a Trovara code change — checks correctness, MVVM layering, security, performance, i18n parity, file-size limits, and test coverage like a senior engineer.
Use when a developer needs orientation to the Trovara codebase — new team member, returning after a gap, or asking "how does X work", "where is Y", or "how do I add a new feature".
Use when a new service, repository, or subsystem needs documentation — CLAUDE.md for new directories, dartdoc for public APIs, or updating existing architecture docs after a structural change.
Use when adding a new screen, modifying existing feature behavior, or wiring new business logic end-to-end in Trovara — creates MVVM scaffold, route, ServiceLocator wiring, and i18n keys.