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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,8 @@ parallel copies under `docs/` or `scripts/notes/`. At cut time: rename
21
21
22
22
- Drop unused `@opentui/keymap`, `@opentui/solid`, and `solid-js`. The interactive TUI is imperative `@opentui/core` only.
23
23
- Restore the opsh skill 1:1 with GaaS. Tool/shell mapping stays on native-integration. user-invocable: false stays so it remains use_skill-only.
24
+
- Restore the pull-request-review skill 1:1 with GaaS. ask_operator, /review mapping, and GitHub posting stay on native-integration. Slash /pull-request-review remains.
25
+
- Ignore GaaS opsh SKILL.md in prettier so table alignment stays 1:1.
24
26
- Restore the git-rebase skill body 1:1 with GaaS. Intern execution recipe stays on native-integration. user-invocable: false stays so it remains use_skill-only.
25
27
- Restore the linear-issue-workflow skill body 1:1 with GaaS. Claim-first, In Review, and git-worktrees extras stay on native-integration. user-invocable: false stays so it remains use_skill-only.
26
28
- Restore the interview skill body 1:1 with GaaS (AskUserQuestion). Operator-ask mapping stays on native-integration. Slash /interview remains.
Copy file name to clipboardExpand all lines: plugins/corbits-skills/skills/native-integration/SKILL.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,8 @@ When the branch under review has an open GitHub pull request, **post the finishe
76
76
77
77
This step is the delivery of the review, not a second pass of analysis. By the time you post, findings are already decided. Do not reopen the read while drafting the body.
78
78
79
+
GaaS pull-request-review loads `code-review` and says "ask the user". Corbits extras: `ask_operator` (tool mapping above), `/review` for `code-review` (slash-name mapping above), and GitHub posting (this section). Do not fork the GaaS pull-request-review body.
git branch -r | grep -E 'origin/(main|master)$'| head -1 | sed 's/.*origin\///'
127
127
```
128
128
129
-
### Step 8: Load the review skill
129
+
### Step 8: Load Code Review Skill
130
130
131
-
Load and follow the `review` skill to perform the actual review. The `review` skill provides guidance on:
131
+
Load and follow the `code-review` skill to perform the actual review. The code-review skill provides guidance on:
132
132
133
133
- Scope determination using git diff
134
134
- Handling pre-existing code
135
135
- Convention compliance
136
136
- Test coverage philosophy
137
137
- Signal over noise (avoiding unactionable findings)
138
138
- Review checklist
139
-
-**Post the Review on GitHub** (required when a PR URL/number is known)
140
-
141
-
### Step 9: Post the Review on GitHub
142
-
143
-
When the review targets a GitHub PR (URL, number, or branch with an open PR), **post the finished review on the PR** before cleanup. A review that only lives in chat is not done.
144
-
145
-
Follow **Post the Review on GitHub** in the `review` skill:
146
-
147
-
1. Map the verdict to a `gh pr review` action:
148
-
- Approve → `--approve`
149
-
- Comment → `--comment`
150
-
- Request changes → `--request-changes`
151
-
2. Body: clean multi-line shape — lens label, one present-tense line on what the branch does, findings with `path:line`, no AI filler. Hard bans live in that skill section.
152
-
3. If additional personas ran (`critic`, `greybeard`, OSS/quality), each lens with substance posts its own labeled review. Primary owns the merge action; secondary lenses use `--comment` only.
153
-
4. Paste the posted review URL(s) into the user-facing summary.
154
-
155
-
Do not skip the post because the chat already summarized the findings.
156
139
157
140
## Cleanup
158
141
@@ -166,7 +149,7 @@ Inform the user that the worktree remains available for further investigation an
166
149
167
150
## Error Handling
168
151
169
-
If any command fails during the workflow, do not retry or attempt workarounds. Stop immediately and `ask_operator` how to proceed. Common failure scenarios include:
152
+
If any command fails during the workflow, do not retry or attempt workarounds. Stop immediately and ask the user for guidance. Common failure scenarios include:
0 commit comments