translation-release-audit

Audit app translations, store listings, and screenshot copy for release readiness.

1.2k|63|Updated Feb 11, 2023
One-click install
npx skills add https://github.com/prof18/feed-flow --skill translation-release-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation-release-audit
Source: https://github.com/prof18/feed-flow/tree/main/.ai/skills/translation-release-audit
Command: npx skills add https://github.com/prof18/feed-flow --skill translation-release-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before shipping a release, it is hard to know whether new translations are complete, whether live App Store, Google Play, and Microsoft Store listings match the source copy in the repo, or whether localized screenshots need regeneration. This Skill automates that release-readiness audit for the FeedFlow project.

Core Features & Use Cases

  • Translation completeness checks: Compares every changed locale's strings.xml against the base values/strings.xml and reports missing or extra keys per locale.
  • Live store drift detection: Reads live Google Play, App Store (via asc), and Microsoft Store (via pcenter) listings and compares them against source copy under assets/storecopy, distinguishing stale live stores from stale checked-in output.
  • Screenshot and follow-up tracking: Flags screenshot copy/assets changes and writes actionable TODO cards to the Obsidian marketing board with exact store, locale, and field names.
  • Use Case: Run a weekly audit to discover that the Russian App Store subtitle is stale while the Google Play listing is current, then get a ready-made board card for the sync work.

Quick Start

Run the translation release audit for the past week and report any store listing or screenshot actions needed.

Frequently Asked Questions about translation-release-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if app translations are complete before a release?

Run the audit to compare each changed locale's strings.xml against the base values/strings.xml. It reports missing and extra keys per locale and marks a locale completed only when no keys are missing.

How to detect stale App Store or Google Play listing metadata?

The audit pulls live metadata using asc for App Store Connect and a Publishing API script for Google Play, then compares it against source copy in assets/storecopy. It distinguishes a stale live store from stale checked-in generated output so you only create upload tasks when needed.

Does the audit modify live store listings or publish changes?

No. All store operations are read-only: it never runs publish tasks, listing push, submissions, or rollouts. Google Play reads use a disposable edit that is deleted, and Microsoft Store checks use only listing show and status commands.

Why does the Microsoft Store description comparison report false differences?

The repo hard-wraps description files at about 80 columns while the Store stores unwrapped text, so raw diffs always differ. The audit normalizes whitespace on both sides before comparing and also detects untranslated placeholder locales that still contain English base text.

What happens when source store copy exceeds App Store field limits?

The audit validates limits before creating follow-up cards: name 30, subtitle 30, keywords 100, description 4000, promotional text 170 characters. Over-limit copy produces a source-shortening card instead of a store sync card.