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: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -891,7 +891,7 @@ The following sets of tools are available:
891
891
-`issue_number`: The number of the issue (number, required)
892
892
-`method`: The read operation to perform on a single issue.
893
893
Options are:
894
-
1. get - Get details of a specific issue.
894
+
1. get - Get issue details. Also returns best-effort hierarchy flags (`has_parent`, `has_children`); `parent` and `sub_issues_summary` are optional relationship summaries.
895
895
2. get_comments - Get issue comments.
896
896
3. get_sub_issues - Get sub-issues (children) of the issue.
897
897
4. get_parent - Get the parent issue, if this issue is a sub-issue of another.
@@ -968,7 +968,8 @@ The following sets of tools are available:
968
968
- 'add' - add a sub-issue to a parent issue in a GitHub repository.
969
969
- 'remove' - remove a sub-issue from a parent issue in a GitHub repository.
970
970
- 'reprioritize' - change the order of sub-issues within a parent issue in a GitHub repository. Use either 'after_id' or 'before_id' to specify the new position.
971
-
(string, required)
971
+
Writes issue hierarchy. To move a sub-issue to a new parent, use `add` with `replace_parent=true`; there is no writable parent field.
972
+
(string, required)
972
973
-`owner`: Repository owner (string, required)
973
974
-`replace_parent`: When true, replaces the sub-issue's current parent issue. Use with 'add' method only. (boolean, optional)
-`confidence`: How confident you are in this choice. Use 'HIGH' for clear signal or explicit user request, 'MEDIUM' for reasonable inference with some ambiguity, 'LOW' for best guess with limited signal. (string, optional)
182
+
-`duplicate_of`: The issue number of the canonical issue this issue duplicates. Only valid when state_reason is 'duplicate'. Required when is_suggestion is true and state_reason is 'duplicate'. The issue number is resolved to a database ID before being sent to the API. (number, optional)
183
+
-`is_suggestion`: If true, this state change is sent to the API as a suggestion (suggest:true) rather than an applied change. Whether the change is applied or recorded as a proposal is determined by the API. (boolean, optional)
181
184
-`issue_number`: The issue number to update (number, required)
182
185
-`owner`: Repository owner (username or organization) (string, required)
186
+
-`rationale`: One concise sentence explaining what specifically about the issue led you to choose this state. State the concrete signal (e.g. 'The reported crash is fixed in v2.1' → completed). (string, optional)
183
187
-`repo`: Repository name (string, required)
184
188
-`state`: The new state for the issue (string, required)
185
189
-`state_reason`: The reason for the state change (only for closed state) (string, optional)
Copy file name to clipboardExpand all lines: pkg/github/__toolsnaps__/issue_read.snap
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@
12
12
"type": "number"
13
13
},
14
14
"method": {
15
-
"description": "The read operation to perform on a single issue.\nOptions are:\n1. get - Get details of a specific issue.\n2. get_comments - Get issue comments.\n3. get_sub_issues - Get sub-issues (children) of the issue.\n4. get_parent - Get the parent issue, if this issue is a sub-issue of another.\n5. get_labels - Get labels assigned to the issue.\n",
15
+
"description": "The read operation to perform on a single issue.\nOptions are:\n1. get - Get issue details. Also returns best-effort hierarchy flags (`has_parent`, `has_children`); `parent` and `sub_issues_summary` are optional relationship summaries.\n2. get_comments - Get issue comments.\n3. get_sub_issues - Get sub-issues (children) of the issue.\n4. get_parent - Get the parent issue, if this issue is a sub-issue of another.\n5. get_labels - Get labels assigned to the issue.\n",
Copy file name to clipboardExpand all lines: pkg/github/__toolsnaps__/sub_issue_write.snap
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@
20
20
"type": "number"
21
21
},
22
22
"method": {
23
-
"description": "The action to perform on a single sub-issue\nOptions are:\n- 'add' - add a sub-issue to a parent issue in a GitHub repository.\n- 'remove' - remove a sub-issue from a parent issue in a GitHub repository.\n- 'reprioritize' - change the order of sub-issues within a parent issue in a GitHub repository. Use either 'after_id' or 'before_id' to specify the new position.\n\t\t\t\t",
23
+
"description": "The action to perform on a single sub-issue\nOptions are:\n- 'add' - add a sub-issue to a parent issue in a GitHub repository.\n- 'remove' - remove a sub-issue from a parent issue in a GitHub repository.\n- 'reprioritize' - change the order of sub-issues within a parent issue in a GitHub repository. Use either 'after_id' or 'before_id' to specify the new position.\nWrites issue hierarchy. To move a sub-issue to a new parent, use `add` with `replace_parent=true`; there is no writable parent field.\n",
Copy file name to clipboardExpand all lines: pkg/github/__toolsnaps__/update_issue_assignees.snap
+38-3Lines changed: 38 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,48 @@
6
6
"readOnlyHint": false,
7
7
"title": "Update Issue Assignees"
8
8
},
9
-
"description": "Update the assignees of an existing issue. This replaces the current assignees with the provided list.",
9
+
"description": "Update the assignees of an existing issue. This replaces the current assignees with the provided list. When setting values, include a confidence level (LOW, MEDIUM, or HIGH) reflecting how certain you are about the choice.",
10
10
"inputSchema": {
11
11
"properties": {
12
12
"assignees": {
13
-
"description": "GitHub usernames to assign to this issue",
13
+
"description": "GitHub usernames to assign to this issue.",
14
14
"items": {
15
-
"type": "string"
15
+
"oneOf": [
16
+
{
17
+
"description": "GitHub username",
18
+
"type": "string"
19
+
},
20
+
{
21
+
"properties": {
22
+
"confidence": {
23
+
"description": "How confident you are in this choice. Use 'HIGH' for clear signal or explicit user request, 'MEDIUM' for reasonable inference with some ambiguity, 'LOW' for best guess with limited signal.",
24
+
"enum": [
25
+
"LOW",
26
+
"MEDIUM",
27
+
"HIGH"
28
+
],
29
+
"type": "string"
30
+
},
31
+
"is_suggestion": {
32
+
"description": "If true, this assignee is sent to the API as a suggestion (suggest:true) rather than an applied assignee. Whether the assignee is applied or recorded as a proposal is determined by the API.",
33
+
"type": "boolean"
34
+
},
35
+
"login": {
36
+
"description": "GitHub username",
37
+
"type": "string"
38
+
},
39
+
"rationale": {
40
+
"description": "One concise sentence explaining what specifically about the issue led you to choose this assignee. State the concrete signal (e.g. 'Authored the file the crash originates in').",
Copy file name to clipboardExpand all lines: pkg/github/__toolsnaps__/update_issue_state.snap
+24-1Lines changed: 24 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,27 @@
6
6
"readOnlyHint": false,
7
7
"title": "Update Issue State"
8
8
},
9
-
"description": "Update the state of an existing issue (open or closed), with an optional state reason.",
9
+
"description": "Update the state of an existing issue (open or closed), with an optional state reason. When closing, include a confidence level (LOW, MEDIUM, or HIGH) reflecting how certain you are about the decision. Use is_suggestion to propose the change without applying it directly.",
10
10
"inputSchema": {
11
11
"properties": {
12
+
"confidence": {
13
+
"description": "How confident you are in this choice. Use 'HIGH' for clear signal or explicit user request, 'MEDIUM' for reasonable inference with some ambiguity, 'LOW' for best guess with limited signal.",
14
+
"enum": [
15
+
"LOW",
16
+
"MEDIUM",
17
+
"HIGH"
18
+
],
19
+
"type": "string"
20
+
},
21
+
"duplicate_of": {
22
+
"description": "The issue number of the canonical issue this issue duplicates. Only valid when state_reason is 'duplicate'. Required when is_suggestion is true and state_reason is 'duplicate'. The issue number is resolved to a database ID before being sent to the API.",
23
+
"minimum": 1,
24
+
"type": "number"
25
+
},
26
+
"is_suggestion": {
27
+
"description": "If true, this state change is sent to the API as a suggestion (suggest:true) rather than an applied change. Whether the change is applied or recorded as a proposal is determined by the API.",
28
+
"type": "boolean"
29
+
},
12
30
"issue_number": {
13
31
"description": "The issue number to update",
14
32
"minimum": 1,
@@ -18,6 +36,11 @@
18
36
"description": "Repository owner (username or organization)",
19
37
"type": "string"
20
38
},
39
+
"rationale": {
40
+
"description": "One concise sentence explaining what specifically about the issue led you to choose this state. State the concrete signal (e.g. 'The reported crash is fixed in v2.1' → completed).",
0 commit comments