[bugsee-ai-skills-sync]

Regenerates the SDK agent skills from bugsee-for-ai.

Changes upstream: bugsee/bugsee-for-ai@ba60a50...54e0541

• Spell check: success
• Site build: success

Generated files must not be edited here — fix the skill in bugsee-for-ai instead.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 5b441cd3-2c0c-4d5f-ae56-a76cd140f07f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[claude]

Claude finished @dsheikherev's task in 23s —— View job

---

Review of #127: sync agent skills from bugsee-for-ai

• Read the diff and the surrounding skill text
• Compare with the hand-written iOS docs
• Run npm run check-skills

Findings

I found no issues in this PR's diff. I'm not posting any inline comments.

What changed: the iOS SKILL.md and v7/SKILL.md have two upstream snippet fixes, and the bugsee-for-ai pin moves forward. The two fixes are in the BugseeAgent size-analysis post-action script.

1. [ ! "$SCRIPT_SRC" ] became [ ! -f "$SCRIPT_SRC" ].
   • The old test only failed on an empty string. In the SPM variant SCRIPT_SRC is always a non-empty hard-coded path, so a wrong path passed the check and then failed later in python3.
   • The new test checks that the file exists, so both the find and SPM variants now fail early with the "BugseeAgent not found" error.
2. SPM path changed from $BUILD_DIR/../SourcePackages/... to ${BUILD_DIR%/Build/*}/SourcePackages/....
   • The old path pointed at .../Build/SourcePackages, which doesn't exist. SourcePackages sits beside Build in DerivedData.
   • The new expansion strips the trailing /Build/... portion, so it resolves to the correct directory. If BUILD_DIR doesn't contain /Build/, the path is left unchanged and the new -f check catches it, so the failure is visible.

Checks run:

• npm run check-skills reports OK — 11 mirrored skills match bugsee-for-ai@54e0541, so there are no hand edits to the generated files.
• The PR body reports spell check and site build as success. I did not re-run either.

Observation (P3, outside this diff, not blocking)

The hand-written pages still use the old empty-string check at these locations:

• docs/sdk/ios/build-size-analysis.mdx:61
• docs/sdk/ios/symbolication.mdx:192
• docs/sdk/ios/v6/symbolication.mdx:200

Those pages use ${BUILD_DIR%Build/*}SourcePackages/..., which resolves to the same directory as the new skill snippet. The only gap is that the check isn't -f, so a wrong SPM path isn't caught early. Consider a follow-up docs PR to align them with the upstream fix. It has no effect on this PR.

Summary

1. Overall risk: Low. The PR changes shell snippets in docs plus a pin bump, and doesn't touch site code.
2. Merge recommendation: Approve and merge. I can't submit a formal approval.
3. Most important issues to fix: none. The optional follow-up is the P3 docs alignment above.
4. Positives:
   • Both upstream fixes correct real bugs.
   • The generated files match the pin.
   • The mirror workflow is working as designed.
     · Branch: automation/sync-agent-skills