Skip to content

Commit 7487163

Browse files
docs: add commit+push step to deploy skill
1 parent 2a6b4f0 commit 7487163

File tree

1 file changed

+18
-5
lines changed

1 file changed

+18
-5
lines changed

.claude/skills/deploy/SKILL.md

Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,25 +12,38 @@ This skill handles manual deployment triggers and troubleshooting. Does NOT hand
1212

1313
## Workflow
1414

15-
### Step 1: Push to master
16-
Deployment is automatic on push to `master`. To trigger manually:
15+
### Step 1: Verify build locally
16+
Run type-check + production build to catch errors before pushing:
17+
```bash
18+
npm run build
19+
```
20+
If build fails, fix errors first — don't push broken code.
21+
22+
### Step 2: Commit and push
23+
Commit pending changes and push to `master` to trigger the deploy workflow:
24+
```bash
25+
git add <changed-files>
26+
git commit -m "feat: <description>"
27+
git push origin master
28+
```
29+
If there are no pending changes but user wants to redeploy, trigger manually:
1730
```bash
1831
gh workflow run deploy-pages.yml
1932
```
2033

21-
### Step 2: Monitor deployment
34+
### Step 3: Monitor deployment
2235
Watch the workflow run:
2336
```bash
2437
gh run list --workflow=deploy-pages.yml --limit 1
2538
gh run watch <run-id> --exit-status
2639
```
2740

28-
### Step 3: Report result
41+
### Step 4: Report result
2942
After successful deploy, inform the user:
3043
- Check the live URL via: `gh api repos/{owner}/{repo}/pages --jq '.html_url'`
3144
- Note: GitHub Pages CDN may take 1-2 minutes to update
3245

33-
### Step 4: First deploy only
46+
### Step 5: First deploy only
3447
If this is the first deployment, configure Pages via API:
3548
```bash
3649
gh api repos/{owner}/{repo}/pages -X PUT -f build_type="workflow"

0 commit comments

Comments
 (0)