菜单
Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans. Use when responding to negative reviews, drafting templates for common review types, or improving review management strategy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
TDD and testing skills for iOS/macOS apps. Covers characterization tests, TDD workflows, test contracts, snapshot tests, test infrastructure, and deterministic quality gates (fitness functions, coverage ratchet, mutation testing). Use for test-driven development, adding tests to existing code, or building test infrastructure.
Set up SwiftUI visual regression testing with swift-snapshot-testing. Generates snapshot test boilerplate and CI configuration. Use for UI regression prevention.
Gate test coverage with a ratchet — a committed baseline that coverage may never drop below and only ever rises. Ships a coverage-gate script (xccov-based) plus an advisory CRAP report (complexity × uncovered). Use when agent-written code needs a deterministic "tests were actually written" check.
Enforce complexity and size limits on Swift code with SwiftLint threshold rules — cyclomatic complexity, function/type/file length, parameter count — adopted via a violations baseline so existing code never blocks. Use when agent-written code needs deterministic size constraints.
Swift language patterns and best practices including concurrency, performance, and modern idioms. Use for Swift language-level code review or architecture guidance.
Write architecture fitness functions — deterministic tests that enforce a project's hard rules (module boundaries, offline guarantees, content contracts) from inside its own test target. Use when a constraint lives only in prose (CLAUDE.md, code review) and should become un-arguable.
| name | review-response-writer |
| description | Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans. Use when responding to negative reviews, drafting templates for common review types, or improving review management strategy. |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","AskUserQuestion"] |
| last_verified | "2026-07-16T00:00:00.000Z" |
| review_by | "2027-06-22T00:00:00.000Z" |
Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans.
| Review Type | Respond? | Priority |
|---|---|---|
| 1-2 stars with feedback | Yes | High |
| 3 stars with suggestions | Yes | Medium |
| Bug reports (any rating) | Yes | High |
| 4-5 stars with content | Yes | Low |
| 4-5 stars generic praise | Optional | Low |
| Abusive/inappropriate | Report, don't respond | - |
| Competitor spam | Report, don't respond | - |
Negative reviews and bug reports: 24-48 hours. Positive reviews: weekly batch is fine. Follow up after fixing an issue to notify the reviewer.
A - Acknowledge their experience
C - Clarify or provide solution
T - Thank them and invite continued feedback
[Greeting - use their name if signed]
[Acknowledge their frustration/praise]
[Address specific points they raised]
[Provide solution, workaround, or update info]
[Thank + future-focused closing]
[Sign-off with name/team]
Review: "App crashes every time I try to export. Waste of money. 1 star."
Response:
Hi [Name],
I'm really sorry about the export crashes — that's frustrating,
especially when you're trying to get work done.
We identified this issue and it's fixed in version X.X, which is
now available. If you update and still experience problems, please
reach out to support@yourapp.com and we'll help you directly.
Thank you for taking the time to report this. It helps us improve.
— [Your Name], [App] Team
Review: "No dark mode? In 2024? Uninstalled."
Response:
Hi there,
You're absolutely right — dark mode is important, and we hear you.
Good news: dark mode is in active development and planned for our
next major update. If you'd like to be notified when it's ready,
drop us a note at support@yourapp.com.
Thanks for the feedback. We hope to welcome you back soon!
— [Your Name], [App] Team
Review: "Can't figure out how to do X. Bad design."
Response:
Hi [Name],
Thanks for reaching out. I can see how [X] might not be obvious
at first — we could definitely make it clearer.
Quick tip: you can access [X] by [simple instructions]. We're also
adding an in-app tutorial in our next update to help with this.
If you're still stuck, email us at support@yourapp.com and we'll
walk you through it.
— [Your Name], [App] Team
Review: "Too expensive for what it does."
Response:
Hi [Name],
Thanks for sharing your thoughts on pricing. I understand — value
is important.
A few things that might help:
• We offer a free trial so you can test before committing
• The subscription includes [key benefits]
• We regularly run promotions — follow us @handle for updates
We're always working to add more value. If there's a specific
feature you'd find worth the price, we'd love to hear about it.
— [Your Name], [App] Team
Review: "Doesn't work. Terrible app."
Response:
Hi there,
I'm sorry to hear you're having trouble. We'd really like to help,
but need a bit more info to figure out what's going wrong.
Could you email us at support@yourapp.com with:
• What you were trying to do
• What happened instead
• Your device and iOS version
We respond quickly and will do our best to get you sorted.
— [Your Name], [App] Team
Review: "Love this app! Would be perfect if it had X."
Response:
Thank you so much for the kind words! 🙏
Great suggestion on [X] — you're not the first to ask, and it's
on our roadmap. Can't promise exact timing, but it's coming.
If you have other ideas, we're all ears at feedback@yourapp.com.
Thanks for being a [App] user!
— [Your Name]
Review: "Great app, use it every day. 5 stars!"
Response:
Thank you! Reviews like this make our day. We're glad [App] is
helping you. If you ever need anything, we're here!
— The [App] Team
Review: [Previously reported bug]
Follow-up Response:
Hi [Name],
Quick update: the [issue] you reported has been fixed in version
X.X, now available in the App Store.
Thank you again for letting us know — you helped us make [App]
better for everyone.
If you get a chance to try the update, we'd love to know if it
resolved things for you.
— [Your Name], [App] Team
| Situation | Tone |
|---|---|
| Bug report | Apologetic, solution-focused |
| Feature request | Appreciative, forward-looking |
| Confusion | Helpful, educational |
| Angry review | Calm, empathetic |
| Positive review | Grateful, personable |
Don't respond. Report to Apple instead if it violates guidelines — profanity, hate speech, personal attacks, or clear spam.
Signs of competitor spam:
Action: Report to Apple, don't engage.
Some users can't be pleased. After one genuine attempt:
If a review contains legal threats: