testflight-feedback-loop is a free skill for Claude Code. Send TestFlight feedback from your phone, open the Claude app, and say “check feedback.” Your Mac at home pulls the feedback, fixes it, and ships the next build to TestFlight. You never sit down at the desk, and Xcode never opens a window.
Two of the four steps happen on your phone. The other two happen on your Mac, without you.
Every build lands in TestFlight. Install it and use your app like anyone else would.
On your phone · TestFlightSpot something? Take a screenshot and send it as TestFlight feedback, with a note.
On your phone · TestFlightOpen the Claude app and say “check feedback.” That’s the whole instruction.
On your phone · Claude appClaude pulls the feedback and crashes, logs each item, fixes it, bumps the build, and uploads.
On your Mac · headless
Building an iPhone app needs a Mac with Xcode, so the work always runs on your Mac. Your phone is the remote. Any coding agent you can message from your phone works, as long as it runs on that Mac.
Remote Control opens your Mac’s Claude Code session in the Claude app. Same session, same files, from anywhere.
claude remote-control. Already in a session? Type /rc.Codex reads the same skill format. The ChatGPT app can control Codex running on your Mac.
~/.codex/skills by default).
The skill is a SKILL.md, two reference files, and two shell scripts. If your agent can read
those and run shell commands on your Mac, and you can message it from your phone, it can run this loop.
Your Mac has to stay awake and online while you’re out. Plug it in and run
caffeinate -dims in a spare terminal, or turn on “Prevent automatic sleeping when the
display is off” in System Settings. If it does sleep, Remote Control reconnects when it wakes.
Set these up one time. After that, the whole loop is your phone.
xcode-select --installbrew install ascbrew install xcodegen.p8 file once, and note the Key ID and Issuer ID.About fifteen minutes, most of it waiting on Apple’s website.
Command line tools, the asc CLI, and Claude Code. Skip any you already have.
$ xcode-select --install $ brew install asc $ brew install xcodegen # only if your project uses project.yml $ curl -fsSL https://claude.ai/install.sh | bash
Make an API key at App Store Connect, Integrations, then save it as a named profile. If you have more than one developer account, make one profile each. The skill checks which one is active before every command.
$ asc auth login \ --name "MyTeam" \ --key-id "ABC123" \ --issuer-id "DEF456" \ --private-key ~/Downloads/AuthKey_ABC123.p8 $ asc auth status --validate
Clone it into Claude Code’s skills folder. For Codex, clone it into ~/.codex/skills instead.
$ git clone https://github.com/fomoPhil/testflight-feedback-loop.git \
~/.claude/skills/testflight-feedback-loop
Optional but good: asc install-skills adds the asc team’s own agent skills, and this skill
hands command-level detail to them when they’re there.
In your app’s folder, start Claude Code and say “ship to TestFlight.” The first run
finds your app ID, scheme and team, and offers to save them in your project’s
CLAUDE.md, so every run after this one is hands-off.
Run claude remote-control in the same folder (or /rc in a running session), and leave
the Mac awake. From here on, everything happens from your phone.
$ cd ~/Projects/MyApp $ claude remote-control --name "MyApp"
Turn on push, so your phone taps you on the shoulder. In Claude Code, run /config and turn on
Push when actions required (permission prompts come to your phone and you approve them there) and
Push when Claude decides (so it can ping you when the build is ready). To make runs quieter, pre-approve
asc, xcodebuild and the skill’s two scripts in your Claude Code permission settings.
Plain words. These are the ones I use from the couch.
| check feedback | Pulls new TestFlight feedback and crash reports, downloads the screenshots, logs every item in testflight-feedback.md, and gives you a short triage list to approve. |
|---|---|
| fix them and ship it | Makes the fixes, runs the build and tests, then ships the next build and marks those items fixed in that build. |
| ship to TestFlight | Checks the asc profile, bumps the build number, archives, exports, uploads, and waits in the background until the build is ready. |
| what’s still open? | Reads the tracker and tells you what’s fixed, what’s open, and what needs a decision from you. |
The skill is strict about the things that go wrong when you’re not watching.
No. Claude Code runs on your Mac, because building an iPhone app needs Xcode, and Xcode only runs on a Mac. The Claude app on your phone is a window into that session. You type, it works at home.
No. Remote Control goes through your Claude account, so your phone can be anywhere with a signal. Your Mac just needs to be awake and online.
No. It ships to TestFlight and stops there. Submitting for review and changing the version number stay with you. For a pre-submission check, see my ios-submission-audit skill.
The skill is plain Markdown and shell scripts, so any agent that reads skills and can run commands on your Mac can use it. I built and tested it with Claude Code. Codex reads the same format, and the ChatGPT app can control Codex on your Mac.
“Check feedback” pulls TestFlight crash reports too, and folds them into the same triage list, so a crash nobody wrote a note about still gets seen.
The skill itself works on any plan that runs Claude Code. Remote Control, the part that lets you drive it from your phone, needs a Pro, Max, Team or Enterprise plan. API keys don’t work with Remote Control.
Yes. MIT license. Read it, change it, make it yours. It’s on GitHub.
Free and open source. One git clone and you’re in.