Skip to content

docs: add agent iOS release skill#39

Open
ertingxihu wants to merge 1 commit into
rorkai:mainfrom
ertingxihu:codex/agent-ios-release-skill-20260611
Open

docs: add agent iOS release skill#39
ertingxihu wants to merge 1 commit into
rorkai:mainfrom
ertingxihu:codex/agent-ios-release-skill-20260611

Conversation

@ertingxihu

@ertingxihu ertingxihu commented Jun 11, 2026

Copy link
Copy Markdown

Summary

  • add an asc-agent-ios-release skill for CLI-first iOS App Store submissions
  • document build/version resolution, dry-run staging, review submission, and hard status verification
  • update README so the new skill is discoverable

Verification

  • reviewed the new skill for placeholder-only examples and no real account secrets
  • checked git diff and README placement

Summary by CodeRabbit

  • Documentation
    • Introduced new iOS App Store release workflow documentation detailing how to use Apple's asc CLI tool for staging and submitting iOS releases.
    • Workflow includes both a detailed release path with validation and metadata staging steps, plus a streamlined one-command approach for quick submissions.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This PR adds documentation for a new asc-agent-ios-release skill. The README registers the skill with usage criteria and an example, while a new SKILL.md file provides comprehensive implementation guidance covering release workflows, operating rules, and handoff specifications for iOS App Store releases using Apple's asc CLI.

Changes

asc-agent-ios-release Skill Documentation

Layer / File(s) Summary
Skill registration and overview
README.md
README registers the asc-agent-ios-release skill with "Use when" checklist and example command for submitting iOS versions and verifying review submission status.
Skill implementation guide
skills/asc-agent-ios-release/SKILL.md
SKILL.md documents the complete workflow: operating rules, release path steps (auth, version/build resolution, validation, metadata staging with dry-run/confirm, review submission with dry-run/confirm, status verification), one-command publish alternative, and handoff schema defining required identifiers and content restrictions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A new skill hops into the warren,
asc-agent-ios-release blazes a path,
From README's bright signpost to SKILL's detailed map,
iOS releases now flow through the Apple Command's wrath,
One workflow documented, no code to defend—
Just words and examples that help agents transcend! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add agent iOS release skill' directly and accurately summarizes the main change: adding documentation for a new iOS release skill to the repository.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@skills/asc-agent-ios-release/SKILL.md`:
- Around line 34-39: Update Step 2 to explicitly show how to resolve both
VERSION/BUILD_ID and PREVIOUS_VERSION: run the existing commands to get VERSION
and BUILD_ID (asc versions list and asc builds info), then add a command using
asc versions list --app "$APP_ID" --platform IOS --state READY_FOR_SALE --output
json (or similar) to locate the latest published version and set
PREVIOUS_VERSION accordingly before Step 4 so that the --copy-metadata-from flag
has a defined value; reference the variables VERSION, BUILD_ID, and
PREVIOUS_VERSION and the asc versions list / asc builds info commands in the doc
update.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9bf11365-3334-4457-9ead-b85513047984

📥 Commits

Reviewing files that changed from the base of the PR and between ed0049a and dc39110.

📒 Files selected for processing (2)
  • README.md
  • skills/asc-agent-ios-release/SKILL.md

Comment on lines +34 to +39
2. Resolve the target version and build:

```bash
asc versions list --app "$APP_ID" --platform IOS --output json
asc builds info --app "$APP_ID" --latest --version "$VERSION" --platform IOS --output json
```

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify the version resolution step.

Step 2 resolves VERSION and BUILD_ID, but later in step 4 (lines 61, 73), the workflow uses $PREVIOUS_VERSION for the --copy-metadata-from flag. The documentation should show how to resolve or identify PREVIOUS_VERSION in this step.

📝 Suggested addition

Consider adding a command to help identify the previous version:

 2. Resolve the target version and build:
 
 ```bash
 asc versions list --app "$APP_ID" --platform IOS --output json
 asc builds info --app "$APP_ID" --latest --version "$VERSION" --platform IOS --output json
+# Identify the previous version if you plan to copy metadata:
+asc versions list --app "$APP_ID" --platform IOS --state READY_FOR_SALE --output json

</details>

<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
2. Resolve the target version and build:

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@skills/asc-agent-ios-release/SKILL.md` around lines 34 - 39, Update Step 2 to
explicitly show how to resolve both VERSION/BUILD_ID and PREVIOUS_VERSION: run
the existing commands to get VERSION and BUILD_ID (asc versions list and asc
builds info), then add a command using asc versions list --app "$APP_ID"
--platform IOS --state READY_FOR_SALE --output json (or similar) to locate the
latest published version and set PREVIOUS_VERSION accordingly before Step 4 so
that the --copy-metadata-from flag has a defined value; reference the variables
VERSION, BUILD_ID, and PREVIOUS_VERSION and the asc versions list / asc builds
info commands in the doc update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant