KeeForge

Prepare and publish an already-built KeeForge version through the App Store Connect website. Use when the user asks to create or finish an App Store version, publish an uploaded build, prepare an App Review submission, stage everything before the final submit, or operate App Store Connect after the release/tag/CI workflow is complete. Covers build processing, export compliance, localized release notes, reviewer information and test fixture, release settings, review staging, and final submission. Do not use for version bumps, release candidates, tags, compatibility gates, or archive creation; use the release skill for those tasks.

Create a new release candidate for the KeeForge iOS app. Bumps the version in project.yml, updates CHANGELOG.md, runs the local KDBX compatibility gate, commits, and pushes an rc/{version} tag so Xcode Cloud and the iOS 18 GitHub Actions workflow run the full test suite; once both gates pass or any test failures pass an exact local-device reproduction, atomically promotes the RC tag to v{version} to trigger the Xcode Cloud build-and-archive workflow. Use this skill whenever the user wants to cut a release, create a release candidate, bump the version, ship a new version, or prepare a build for TestFlight/App Store. Triggers on phrases like "release", "new version", "bump version", "cut a release", "prepare release", "ship it", "release candidate", or "push a new build".

Turn a feature request into implementation-ready spec files for a coding agent. Use whenever the user wants to plan, scope, or write a spec for a feature about to be built: "write a spec for X", "plan feature Y", "how should we build Z", "draft an implementation plan". Produces a parent epic plus one file per independently-buildable slice. Prefer this skill when the audience is a coding agent, not an exec. Auto-applies the KeeForge overlay when the repo looks like KeeForge.