Skip to content

Commit 9391539

Browse files
committed
🔧 chore: add deploy-testflight skill for TestFlight release tagging
1 parent 8da9326 commit 9391539

File tree

2 files changed

+31
-0
lines changed

2 files changed

+31
-0
lines changed
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: deploy-testflight
3+
description: "Create and push SNUTT iOS TestFlight deployment tags by asking for version, environment (dev/prod), and a one-word change slug, following README.md tag rules. Use when a user asks to deploy to TestFlight, tag a TestFlight release, or push TestFlight tags for SNUTT iOS."
4+
---
5+
6+
# Deploy TestFlight tags (SNUTT iOS)
7+
8+
## Workflow
9+
10+
- Read `README.md` in the repo and follow the Deployment > Tag Format rules.
11+
- Ask the user for:
12+
- Deployment version (e.g., `4.0.0`).
13+
- Environment: `dev` or `prod`.
14+
- One-word change slug (short, lowercase, letters/numbers/hyphens). This is required.
15+
- Build the tag:
16+
- `dev` => `testflight/dev/v{version}-{slug}`
17+
- `prod` => `testflight/v{version}-{slug}`
18+
- Verify the tag does not already exist: `git tag -l <tag>`.
19+
- If it exists, stop and ask for a different version or slug. Do not delete tags unless explicitly asked.
20+
- Create the tag on current HEAD: `git tag <tag>`.
21+
- Push the tag: `git push origin <tag>`.
22+
- Report the created tag and the push result.
23+
24+
## Notes
25+
26+
- Do not create `appstore/` tags in this workflow.
27+
- If the user wants to re-deploy the same version, insist on a new slug.
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
interface:
2+
display_name: "Deploy TestFlight"
3+
short_description: "Create/push SNUTT TestFlight tags"
4+
default_prompt: "Use $deploy-testflight to tag and push a SNUTT iOS TestFlight release."

0 commit comments

Comments
 (0)