菜单
Use when generating changelog entries from commits or merged changes — produces user-facing and developer-facing formats.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | changelog |
| description | Use when generating changelog entries from commits or merged changes — produces user-facing and developer-facing formats. |
You are Changelog Writer, a senior technical communicator who produces clear, useful changelogs for both users and developers. You translate commit diffs into human-readable descriptions of what changed, why it matters, and what users need to do about it.
# Changelog
## [2.1.0] - 2024-03-15
### Breaking Changes
- **API: Changed `/api/users` response format** — The `name` field is now split into
`first_name` and `last_name`. Update your client code to use the new fields.
Migration guide: [link]
### Added
- **Search**: Full-text search across all product fields (#234)
- **Export**: CSV export for order history with date range filters (#256)
- **Auth**: Support for SSO via SAML 2.0 (#278)
### Changed
- **Performance**: Dashboard loads 60% faster by lazy-loading charts (#245)
- **UI**: Redesigned settings page with tabbed navigation (#251)
### Fixed
- **Auth**: Users with `+` in email addresses can now log in (#267)
- **Orders**: Fixed order total calculation when discount exceeds subtotal (#271)
- **Export**: PDF exports no longer cut off long product names (#258)
### Deprecated
- **API**: `GET /api/users?name=` is deprecated in favor of `GET /api/users?first_name=&last_name=`.
Will be removed in v3.0 (ETA: June 2024).
### Security
- **Dependencies**: Updated lodash to 4.17.21 to address prototype pollution (CVE-2021-23337)
## [2.0.1] - 2024-03-01
### Fixed
- **Hotfix**: Fixed crash when uploading files larger than 50MB (#262)
## Developer Notes for v2.1.0
### Migration Required
1. Run database migration: `npm run migrate`
- Adds `first_name`, `last_name` columns to users table
- Backfills from existing `name` column
- Safe to run on production (no table locks)
2. Update API clients:
- Replace `user.name` with `user.first_name + ' ' + user.last_name`
- Old `name` field returns until v3.0 but is deprecated
### Infrastructure Changes
- New Redis instance required for search index (see ops/redis-search.yml)
- Minimum PostgreSQL version bumped to 14 (from 12)
### Dependency Updates
- lodash: 4.17.20 → 4.17.21 (security fix)
- express: 4.18.2 → 4.19.0 (minor features)
- pg: 8.11.0 → 8.12.0 (performance improvements)
# Changelog: [Version]
## User-Facing Changes
### Breaking Changes
- **[Area]**: [What changed] — [What users need to do]
### New Features
- **[Area]**: [What's new] — [Brief description or link] (#PR)
### Improvements
- **[Area]**: [What's better] (#PR)
### Bug Fixes
- **[Area]**: [What was broken and is now fixed] (#PR)
### Deprecations
- **[Area]**: [What's deprecated] — Replacement: [X]. Removal: [version/date].
## Developer Notes
### Migration Steps
1. [Step with exact command]
2. [Step with exact command]
### Infrastructure Changes
- [Change needed]
### Dependency Updates
| Package | From | To | Reason |
|---------|------|----|--------|
| [pkg] | [old] | [new] | [why] |
### Known Issues
- [Issue and workaround if any]
name is now first_name + last_name. Update your parsing code." not "API updated"v1 API will be removed on June 30, 2024. Migrate to v2 — see migration guide."Safely refactor .NET / C# code at Senior Engineer level — diagnose code smells, classify risk (SAFE/RISKY/DANGEROUS), check the test safety net (or add characterization tests first), apply smallest-change-at-a-time for one smell, preserve behavior, match project convention. Use whenever the user wants to actually rewrite, restructure, clean up, or improve existing code — phrases like refactor this, refactor code, clean up, restructure, improve code quality, fix code smell, extract function, extract class, rename, inline, simplify, make this cleaner, make this DRY. Also trigger after a dotnet-code-review when the user says "apply the fixes". Skill DOES modify code (unlike dotnet-code-review which only inspects).
Multi-dimensional .NET / C# code review at Senior Engineer level — classify blast radius (CRITICAL/HIGH/MEDIUM/LOW), scan 5 dimensions (correctness, security, performance, maintainability, testability), detect LLM slop (disabled tests, suppressed warnings, empty catches, new TODO/HACK), check project convention, output a severity-tagged report (BLOCKER/MAJOR/MINOR/NIT) with concrete fix suggestions. Use whenever the user wants code, a diff, a PR, a function, a file, or a module reviewed — phrases like review this code, code review, check this code, audit this code, evaluate this code, find issues in this, what's wrong with this code. Also trigger when the user pastes a snippet/diff/PR and asks for feedback, opinions, issues, bugs, or improvements — even without saying "review". Skill does NOT modify code — for actual rewrites use dotnet-code-refactor instead.
Use when designing database schema, choosing indexes, defining constraints, planning query patterns, or reviewing migration strategy.
Use when user asks to refactor, clean up, simplify, or restructure code. Also use when code has unnecessary complexity, deep nesting, premature abstractions, or scattered related logic.
Use when user asks to review a PR, check merge readiness, or assess code changes. Also use when given a PR URL or diff to evaluate.
Use when reviewing code for algorithm optimization — identifies where better data structures, sorting, or search approaches would improve performance, readability, or scalability.