App Store Review Sentiment and Release Notes Automation Script
Build a Python script that pulls app store consumer reviews, identifies retail checkout friction, and outputs drafted release notes.
Use this prompt when building developer tooling to monitor retail app feedback following a major update. It creates an automation script that connects to app store developer APIs, filters reviews by keyword, and summarizes key UX issues.
Role: Lead Mobile Growth Engineer in Retail eCommerce data operations.
Context
- Retail application store ID: {{retail_app_id}}
- API credential environment variable: {{api_credentials_env_var}}
- Reporting analysis cadence: {{reporting_cadence}}
- Checkout friction keywords: {{checkout_friction_keywords}}
- Star rating filter threshold: {{min_star_rating_filter}}
- Destination alert webhook: {{slack_webhook_destination}}
Task
Create a production Python script that fetches recent customer reviews for {{retail_app_id}} via official store APIs, extracts consumer sentiment around {{checkout_friction_keywords}}, and prepares a formatted release remediation summary sent to {{slack_webhook_destination}}.
Method
- Authenticate against the store API using credentials loaded from {{api_credentials_env_var}}.
- Fetch all review submissions received over the specified {{reporting_cadence}}.
- Filter customer feedback entries matching ratings at or below {{min_star_rating_filter}}.
- Scan review content for occurrences and semantic variations of {{checkout_friction_keywords}} (e.g., payment failure, coupon error, scanning bug).
- Cluster common complaints into prioritized UX pain points with customer impact scores.
- Format an actionable summary containing verbatim quotes and proposed developer patch notes.
- Dispatch the aggregated payload as a formatted rich message card to {{slack_webhook_destination}}.
Constraints
- Script MUST use Python 3.10+ standard libraries alongside
requestsorurllib. - MUST implement API rate-limiting checks and handle HTTP 429 backoff gracefully.
- Customer personal data (names, email strings) MUST NOT be relayed in raw Slack messages.
- Execute cleanly as a scheduled cron or CI/CD scheduled pipeline step.
Output format
1. Script Dependencies and CLI Invocation
Requirements block and execution command examples.
2. Python Feedback Extraction Script
Complete, modular Python source file with docstrings, type annotations, and main execution entry.
3. Webhook Card Preview
Sample JSON payload illustrating the Slack alert structure sent to development teams.
Self-review
- Ensure keyword scanning is case-insensitive and resilient to minor typos.
- Verify authentication respects store API token rotation and expiry limits.
- Check that the star rating threshold filtering strictly isolates high-priority negative friction.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.