You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Commit already-staged changes and push in one step. Use when the user asks to "commit and push staged changes", "commit and push what's staged", or "commit staged and push".
Copy file name to clipboardExpand all lines: skills/commit-staged/SKILL.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: commit-staged
3
-
description: Commit already-staged changes with a message matching existing commit style. Use when the user asks to "commit staged changes", "commit what's staged", "commit these changes", "commit my changes", or "make a commit".
3
+
description: Commit already-staged changes with a message matching existing commit style. Use when the user asks to "commit staged changes" or "commit what's staged".
Copy file name to clipboardExpand all lines: skills/resolve-pr-comments/SKILL.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,18 +40,14 @@ Run the `/evaluate-findings` skill on the unresolved threads to assess each comm
40
40
41
41
Run the `/self-improve` skill.
42
42
43
-
## Step 4: Stageand Commit
43
+
## Step 4: Stage, Commit, and Push
44
44
45
-
If any fixes were applied, use `AskUserQuestion` to ask if the user wants to stageand commit the changes now.
45
+
If any fixes were applied, use `AskUserQuestion` to ask if the user wants to stage, commit, and push the changes now.
46
46
47
-
-**Yes** — run the `/stage-commit` skill
47
+
-**Yes** — run the `/stage-commit-push` skill
48
48
-**No** — leave changes unstaged, proceed to replies
49
49
50
-
## Step 5: Wait for Push
51
-
52
-
Use `AskUserQuestion` to ask if the user has already pushed. Wait for confirmation before proceeding to replies.
53
-
54
-
## Step 6: Reply to Each Thread
50
+
## Step 5: Reply to Each Thread
55
51
56
52
Run `/github-voice` to load writing style rules before composing replies. Keep replies to one or two sentences. Avoid bullet-point reasoning or bolded labels.
57
53
@@ -75,7 +71,7 @@ Only add a brief description after the SHA if the fix meaningfully diverges from
75
71
76
72
**Reply format for skips:** Just state the reasoning for not changing it.
77
73
78
-
## Step 7: Summary
74
+
## Step 6: Summary
79
75
80
76
After processing all threads, present a summary table:
description: Stage files, create a commit, and push in one step. Use when the user asks to "stage commit and push", "add commit and push", "commit and push", or "commit and push my changes".
Copy file name to clipboardExpand all lines: skills/stage-commit/SKILL.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: stage-commit
3
-
description: Stage files and create a commit in one step with a message matching existing commit style. Use when the user asks to "stage and commit", "add and commit", "commit these files", or "stage my changes and commit".
3
+
description: Stage files and create a commit in one step with a message matching existing commit style. Use when the user asks to "stage and commit", "add and commit", "commit my changes", or "commit these changes".
0 commit comments