AP
app-store-testflight-release
Use this skill for TestFlight, App Store Connect, release checklists, screenshots, review notes, versioning. Trigger when the task involves apps work related to App Store Testflight Release, production implementation, audits, debugging, strategy, or validation.
Install
mkdir -p .claude/skills/app-store-testflight-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13505" && unzip -o skill.zip -d .claude/skills/app-store-testflight-release && rm skill.zipInstalls to .claude/skills/app-store-testflight-release
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill for TestFlight, App Store Connect, release checklists, screenshots, review notes, versioning. Trigger when the task involves apps work related to App Store Testflight Release, production implementation, audits, debugging, strategy, or validation.261 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
About this skill
App Store Testflight Release
Use this skill to handle Apps tasks focused on TestFlight, App Store Connect, release checklists, screenshots, review notes, versioning.
Workflow
- Clarify the user outcome, constraints, current stack, and definition of done.
- Inspect the local repository or provided artifacts before proposing changes.
- Check official documentation when APIs, platform rules, SDK versions, policies, or production behavior may have changed.
- For non-trivial choices, compare proven open-source patterns or examples and adapt ideas without copying incompatible code.
- Implement the smallest production-ready change that satisfies the request.
- Validate with the most relevant checks: tests, lint, typecheck, build, browser/device review, audits, or manual scenario.
- Report changed files, commands run, remaining risks, and exact next steps.
Focus Checklist
- Define scope and assumptions explicitly.
- Prefer existing project conventions and tools.
- Handle loading, empty, error, permission, and edge states where relevant.
- Include security, privacy, performance, accessibility, and rollback considerations when they apply.
- Keep output actionable and evidence-backed.
Guardrails
- Do not submit apps or change store metadata without explicit confirmation.
- Do not perform destructive, paid, production, trading, publishing, or account-changing actions without explicit user confirmation.
- Do not expose secrets, private keys, tokens, cookies, personal data, or confidential business data.
- If validation is impossible, state exactly why and provide a manual verification path.