Use when setting up DocC documentation for a Swift package, deploying to GitHub Pages, or encountering "no such module 'UIKit'" during doc generation
91
—
Does it follow best practices?
Impact
83%
1.53xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Cross-platform Swift DocC GitHub Pages workflow
swift-docc-plugin dependency
50%
100%
Correct generate-doc command
40%
100%
disable-indexing flag
0%
100%
Correct hosting-base-path
0%
100%
Workflow file path
100%
100%
Correct permissions
100%
100%
Correct triggers
100%
100%
Concurrency group
50%
100%
checkout action version
0%
100%
upload-pages-artifact version and path
50%
100%
deploy-pages action version
100%
100%
Deploy job structure
16%
100%
Redirect index.html
0%
100%
Lowercase target in URL
100%
100%
iOS-only Swift package DocC GitHub Actions workflow
xcodebuild docbuild used
0%
100%
iOS Simulator destination
0%
100%
xcrun docc process-archive
0%
100%
Correct .doccarchive path
0%
100%
Redirect index.html added
100%
100%
Lowercase target name in redirect
100%
100%
setup-xcode action
100%
100%
Correct action versions
42%
100%
Workflow permissions
100%
100%
Concurrency configuration
100%
100%
Correct triggers
60%
100%
Build job on macos-latest
100%
100%
Deploy job structure
40%
100%
hosting-base-path REPO_NAME
100%
100%
upload-pages-artifact path
66%
100%
Fix broken iOS DocC GitHub Pages workflow
Uses xcodebuild docbuild
100%
100%
iOS Simulator destination
0%
0%
docc process-archive step
100%
100%
.doccarchive path under iphonesimulator
0%
25%
hosting-base-path set
100%
100%
Redirect index.html added
100%
0%
URL uses lowercase target
100%
100%
Correct upload action version
0%
0%
Correct deploy action version
0%
0%
Correct checkout action version
0%
0%
Root cause explained
100%
100%
Public types warning
100%
20%
af7cba7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.