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
refactor: use backtick tool references in skill body content
Update all 16 skill definitions to use explicit backtick-formatted
tool names with '## Available Tools' sections instead of bold markdown
references. This makes tool names more reliably parseable by models
that consume the SKILL.md content via load_skill.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
For search tools, use separate **sort** and **order** parameters — do not include 'sort:' syntax in query strings. Query strings should contain only search criteria (e.g., 'org:google language:python').
107
+
For search tools, use separate `+"`sort`"+` and `+"`order`"+` parameters — do not include 'sort:' syntax in query strings. Query strings should contain only search criteria (e.g., 'org:google language:python').
- `+"`add_comment_to_pending_review`"+` — add a line comment to a pending review
215
+
- `+"`add_reply_to_pull_request_comment`"+` — reply to a PR review comment
216
+
- `+"`update_pull_request_title`"+` — update a PR's title
217
+
- `+"`update_pull_request_body`"+` — update a PR's body
218
+
- `+"`update_pull_request_state`"+` — update a PR's state (open/closed)
219
+
- `+"`update_pull_request_draft_state`"+` — convert between draft and ready
220
+
- `+"`request_pull_request_reviewers`"+` — request reviewers for a PR
221
+
- `+"`create_pull_request_review`"+` — create a new PR review
222
+
- `+"`submit_pending_pull_request_review`"+` — submit a pending review
223
+
- `+"`delete_pending_pull_request_review`"+` — delete a pending review
224
+
- `+"`add_pull_request_review_comment`"+` — add a review comment to a PR
225
+
- `+"`resolve_review_thread`"+` — resolve a review thread
226
+
- `+"`unresolve_review_thread`"+` — unresolve a review thread
227
+
182
228
## PR Review Workflow
183
229
For complex reviews with line-specific comments:
184
-
1. Use **pull_request_review_write** with method 'create' to create a pending review.
185
-
2. Use **add_comment_to_pending_review** to add line comments.
186
-
3. Use **pull_request_review_write** with method 'submit_pending' to submit the review.
230
+
1. Call `+"`create_pull_request_review`"+` or `+"`pull_request_review_write`"+` with method 'create' to create a pending review.
231
+
2. Call `+"`add_comment_to_pending_review`"+` to add line comments.
232
+
3. Call `+"`submit_pending_pull_request_review`"+` or `+"`pull_request_review_write`"+` with method 'submit_pending' to submit.
187
233
188
234
## Creating Pull Requests
189
235
Before creating a PR, search for pull request templates in the repository. Template files are called pull_request_template.md or located in the '.github/PULL_REQUEST_TEMPLATE' directory. Use the template content to structure the PR description.
190
-
191
-
## Tool Selection
192
-
- Use **search_pull_requests** for targeted queries with specific criteria.
193
-
- Use **list_pull_requests** for broad retrieval with basic filtering and pagination.
- `+"`projects_list`"+` — list projects for a user, org, or repo
332
+
- `+"`projects_get`"+` — get project details, fields, items, or status updates
333
+
- `+"`projects_write`"+` — create/update/delete project items, fields, or status updates
334
+
278
335
## Workflow
279
-
1. Call **projects_list** to find projects.
280
-
2. Use **projects_get** with list_project_fields to understand available fields and get IDs/types.
281
-
3. Use **projects_get** with list_project_items (with pagination) to browse items.
282
-
4. Use **projects_write** for updates.
336
+
1. Call `+"`projects_list`"+` to find projects.
337
+
2. Call `+"`projects_get`"+` with list_project_fields to understand available fields and get IDs/types.
338
+
3. Call `+"`projects_get`"+` with list_project_items (with pagination) to browse items.
339
+
4. Call `+"`projects_write`"+` for updates.
283
340
284
341
## Status Updates
285
342
Use list_project_status_updates to read recent project status updates (newest first). Use get_project_status_update with a node ID to get a single update. Use create_project_status_update to create a new status update.
0 commit comments