Claude Skills para Android e Play Store
kanetik/claude-skills
Tradução, release notes e revisão de PRs para Android e Play Store
Ver no GitHubColeção de skills para Claude Code focada em localização de apps Android e conteúdo Play Store. Inclui tradução de strings, geração de release notes, tradução de conteúdo marketing e loop iterativo de revisão de PRs. Cada skill é single-purpose e composto para workflows específicos.
Instalação
npx convez-ai kanetik/claude-skills1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Traduzir strings.xml para múltiplas locales mantendo placeholders e plurais
- Gerar release notes Play Store a partir de commit log
- Traduzir descrições e marketing copy com limites de caracteres
- Executar loops iterativos de revisão de PR com múltiplos reviewers
Veredito

Conjunto bem estruturado de skills especializados em localização Android, com design modular e composável. Ideal para times que trabalham com múltiplos idiomas e precisam de automação robusta em workflows de release.
README
A tradução para o português deste README ainda está na fila.
Claude Skills
A collection of Claude Code skills I find useful and worth sharing. It isn't tied to one domain — whatever makes a good, self-contained skill can live here. (Several of the skills so far happen to deal with localization for Android and Play Store content, but that's just where I started, not the theme.)
The skills here are deliberately small and single-purpose. Each one does one job and nothing more: it takes inputs, applies the expert work, and stops. A skill doesn't reach outside its own job — figuring out what to feed it (git ranges, "last PR", "what changed since master") is the conversation's job, and side concerns like committing or opening PRs belong to the caller unless that work is the skill's actual domain (a skill built to run a PR-review loop legitimately drives git and PRs — that's the point of it). Compose the small transforms with whatever commit/PR skills you already use.
What's in here
| Skill | What it does |
|---|---|
/translate-strings | Translate Android values/strings.xml keys into every sibling values-{locale}/strings.xml. Preserves placeholders, escapes, plurals, HTML, translatable="false". Always writes locale files alphabetized by key. Supports --add <locale> for onboarding and --retranslate <key> to force a fresh pass. |
/translate-content | Translate prose — Play Store release notes, app descriptions, FAQs, marketing copy. Reads a per-repo config for output layout, target locales, and char limits. Handles cross-sentence consistency, tone, and the 500-char Play Store limit. |
/whats-new | Author Play Store "What's New" release notes from your commit log (English only). Pulls commits since the last release tag, drafts bullets within Play's 500-char limit, waits for approval, then writes the source-locale file and hands off to /translate-content for the other locales. |
/pr-review-loop | Run an iterative PR review loop on a repo's open PR(s): request AI reviewers (Copilot, Codex, any bot that posts), wait for their reviews, evaluate each thread under a weighted project/PR/item judgement, then fix, push back, or file follow-up issues, and repeat until every tracked bot is satisfied. Self-contained — bundles config defaults and reference material, reads project overrides from the consuming repo, and degrades gracefully where loop/scheduling primitives are absent. Driving git/PRs is this skill's actual job, not overreach. |
Typical workflow
Translating a feature branch's new strings after review settles:
- You: "find what strings changed since master, then translate them"
- Claude (the conversation): runs
git diff master -- 'app/src/main/res/values/strings.xml', identifies the changed keys, shows them to you - Claude invokes
/translate-stringswith the source path + the explicit key list - The skill writes the locale files and prints a summary
- You commit however you normally do
Forgot to translate before merge? "translate the strings from the last PR" — the conversation resolves the PR commit, identifies the diff, calls the skill.
Cutting a release? /whats-new drafts the English release notes from your commits, you approve, then /translate-content propagates to the other locales.
Just opened a PR? /pr-review-loop takes it from there — it requests the AI reviewers, waits for them, works through their feedback (fixing, pushing back, or filing follow-ups), and loops until they're satisfied. Unlike the translation skills, this one is about git/PR work, so it drives those operations itself rather than leaving them to you.
Installation
Option A — Claude Code plugin (recommended)
In Claude Code:
/plugin install kanetik/claude-skills
This wires the skills in via the .claude-plugin/plugin.json manifest.
Option B — clone + symlink
If you'd rather keep a local checkout you can hack on:
git clone https://github.com/kanetik/claude-skills.git ~/Projects/claude-skills
Then symlink each skill into your ~/.claude/skills/ directory.
macOS / Linux:
ln -s ~/Projects/claude-skills/skills/translate-strings ~/.claude/skills/translate-strings
ln -s ~/Projects/claude-skills/skills/translate-content ~/.claude/skills/translate-content
ln -s ~/Projects/claude-skills/skills/whats-new ~/.claude/skills/whats-new
Windows (directory junctions, no admin required):
mklink /J "%USERPROFILE%\.claude\skills\translate-strings" "%USERPROFILE%\Projects\claude-skills\skills\translate-strings"
mklink /J "%USERPROFILE%\.claude\skills\translate-content" "%USERPROFILE%\Projects\claude-skills\skills\translate-content"
mklink /J "%USERPROFILE%\.claude\skills\whats-new" "%USERPROFILE%\Projects\claude-skills\skills\whats-new"
Option C — plain copy
If you don't want the link / want to fork-and-modify locally without syncing back:
cp -r ~/Projects/claude-skills/skills/translate-strings ~/.claude/skills/
cp -r ~/Projects/claude-skills/skills/translate-content ~/.claude/skills/
cp -r ~/Projects/claude-skills/skills/whats-new ~/.claude/skills/
Per-project setup
The skills are project-agnostic — they don't hardcode any paths, brand names, or layouts. To wire a project in:
For /translate-strings
No config needed. The skill operates on standard Android resource layout (app/src/main/res/values/strings.xml and sibling values-{locale}/strings.xml). Project-specific brand names (the things that should not be translated) belong in your project's CLAUDE.md so the conversation can pass them through as guidance.
For /translate-content and /whats-new
Add a .claude/whats-new.config.md (or .claude/translate-content.config.md) at your repo root with:
output_dir: app/src/main/play/release-notes # gradle-play-publisher layout
file_pattern: "{locale}/default.txt"
# or for r0adkll/upload-google-play layout:
# output_dir: playstore/whatsnew
# file_pattern: whatsnew-{locale}
locales:
- en-US (default)
- de-DE
- es-ES
- fr-FR
# ... etc
char_limit: 500
since_ref_rule: "last tag matching ^[0-9]+\\.[0-9]+\\.[0-9]+$"
The skills read this once per invocation and use it to find the source file, list the target locales, and enforce the char limit.
Design principles
If you want to add to this collection (or fork it for your own), these are the rules I'm holding myself to:
- Does its job and nothing more. Inputs → expertise → outputs. A skill doesn't bolt on concerns outside its stated job or impose workflow the caller didn't ask for. Git operations, commits, pushes, and PRs are normally the caller's concern — unless they are the skill's actual domain, in which case doing them is the whole point.
- Single responsibility. One skill, one thing.
/translate-stringsand/translate-contentare separate because XML resources and prose are different domains with different rules — better than one/translatewith internal dispatch. - Self-contained and dependency-light. A skill stands on its own when its folder is dropped into
~/.claude/skills/— everything it needs lives inside the folder. Reference bundled files fromSKILL.mdby paths relative toSKILL.md(the documented supporting-files pattern; Claude resolves them against the skill's own directory, not the working directory). Files executed from a bash-injection command use the${CLAUDE_SKILL_DIR}substitution, since the working directory at run time is the project root. No absolute~/.claude/...assumptions. It doesn't demand tools a typical user wouldn't have; where a real dependency exists (gh,jq), it's stated, not silently assumed. - Project-agnostic. No project-specific brand names, paths, or conventions baked into the skill. Those go in per-repo config files or per-repo
CLAUDE.md. - Composable. A skill should work the same whether the caller is a human typing a slash command, another skill, or a script. No assumptions about who's calling.
- Conservative defaults. Don't do expensive work that wasn't asked for — e.g. don't re-translate what's already translated. The user can always force it.
Contributing
Issues and PRs welcome. If you want to add a skill, please follow the principles above — small, single-purpose, self-contained, and scoped to one job (don't reach outside what the skill is actually for).