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
{{ message }}
Repository navigation
Commit f9f538d
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/create-github-issue/SKILL.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,16 +17,21 @@ This project uses YAML form issue templates. When creating issues, match the tem
17
17
18
18
### Bug Reports
19
19
20
-
Do not add a type label automatically. The body must include an **Agent Diagnostic** section — this is required by the template and enforced by project convention. Apply area or topic labels only when they are clearly known.
20
+
Do not add a type label automatically. The body must include an **Agent Diagnostic** section — this is required by the template and enforced by project convention. The diagnostic must identify the OpenShell version tested, whether the latest release or known fixes were checked, and whether possible duplicate issues were searched. If the agent cannot verify the latest release or search existing issues, say so explicitly instead of guessing. Apply area or topic labels only when they are clearly known.
21
21
22
22
```bash
23
23
gh issue create \
24
24
--title "bug: <concise description>" \
25
25
--body "$(cat <<'EOF'
26
26
## Agent Diagnostic
27
27
28
-
<Paste the output from the agent's investigation. What skills were loaded?
29
-
What was found? What was tried?>
28
+
- Skills loaded: <skills used during investigation>
29
+
- OpenShell version tested: <version from openshell --version or other source>
30
+
- Latest release checked: <version checked, or unable to verify>
31
+
- Known fixes reviewed: <release notes / merged PRs checked, or unable to verify>
32
+
- Possible duplicates reviewed: <existing issues searched, or unable to verify>
33
+
- Findings: <what the agent found and tried>
34
+
- Remaining reason for filing: <why this still appears to be a bug>
30
35
31
36
## Description
32
37
@@ -44,6 +49,8 @@ What was found? What was tried?>
44
49
- OS: <os>
45
50
- Docker: <version>
46
51
- OpenShell: <version>
52
+
- Latest release checked: <yes/no and reason>
53
+
- Possible duplicates checked: <yes/no and reason>
Copy file name to clipboardExpand all lines: .agents/skills/triage-issue/SKILL.md
+23-6Lines changed: 23 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Query all open issues with the `state:triage-needed` label and process them in s
51
51
gh issue list --label "state:triage-needed" --state open --json number,title --jq '.[].number'
52
52
```
53
53
54
-
For each issue returned, run the full triage workflow (Steps 1-6). Report a summary at the end listing each issue and its classification.
54
+
For each issue returned, run the full triage workflow (Steps 1-7). Report a summary at the end listing each issue and its classification.
55
55
56
56
## Step 1: Fetch the Issue
57
57
@@ -89,7 +89,23 @@ Check whether the issue body contains a substantive agent diagnostic section. Lo
89
89
90
90
**If the diagnostic section is substantive**, proceed to Step 4.
91
91
92
-
## Step 4: Diagnose and Validate
92
+
## Step 4: Check Reported Version and Known Fixes
93
+
94
+
Before deeper diagnosis, determine whether the report may already be fixed in a newer release.
95
+
96
+
1. Extract the reported OpenShell version from the issue body, Agent Diagnostic, environment section, logs, and comments. If no version is provided, record that as missing context and continue.
97
+
2. Check current release information and known fixes when available:
98
+
-`gh release list --limit 10`
99
+
-`gh release view <tag>`
100
+
- linked issues, merged PRs, release notes, and local git tags/history
101
+
3. If network access or release metadata is unavailable, state the limitation in the triage comment instead of guessing.
102
+
103
+
If the issue targets an older OpenShell release and a newer release or merged PR appears to address the same behavior:
104
+
105
+
- If the reporter has already reproduced the issue on the fixed/current release, continue to Step 5.
106
+
- If the reporter has not tested the fixed/current release, use the `fixed-in-release` classification in Step 6. Reference the fixing version and PR/issue when known, and ask for a fresh report or reopen if the issue still reproduces on that version.
107
+
108
+
## Step 5: Diagnose and Validate
93
109
94
110
Assess the report by investigating the codebase. Use the `principal-engineer-reviewer` sub-agent via the Task tool:
95
111
@@ -114,20 +130,21 @@ Based on the sub-agent's analysis, also attempt to validate the report directly:
114
130
- For inference and provider-topology issues: reference the `debug-inference` skill's known failure patterns
115
131
- For CLI/usage issues: reference the `openshell-cli` skill's command reference
116
132
117
-
## Step 5: Classify
133
+
## Step 6: Classify
118
134
119
135
Based on the investigation, classify the issue into one of these categories:
120
136
121
137
| Classification | Criteria | Action |
122
138
|---------------|----------|--------|
123
139
|**bug-confirmed**| Agent diagnostic and codebase analysis confirm a real defect | Apply relevant `area:*` or `topic:*` labels as needed, remove `state:triage-needed`, and assign the built-in `Bug` issue type manually if needed |
124
140
|**feature-valid**| Design proposal is sound, feasible given the architecture | Apply relevant `area:*` or `topic:*` labels as needed, remove `state:triage-needed`, and assign the built-in `Feature` issue type manually if needed |
141
+
|**fixed-in-release**| Report targets an older OpenShell release and a newer release or merged PR appears to address the behavior; no fixed/current-release reproduction is provided | Comment with the fixing version and PR/issue when known. Close as completed when the fix is clear, or request a retest if confirmation is still needed. Remove `state:triage-needed` when closing |
125
142
|**duplicate**| An existing open issue covers this | Link the duplicate, close with comment |
126
143
|**user-error**| The reported behavior is expected, or the issue is a misconfiguration | Comment with explanation and guidance, close |
127
144
|**needs-more-info**| Report is substantive but missing critical reproduction details | Comment requesting specifics, keep `state:triage-needed`|
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.yml
+13-2Lines changed: 13 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -9,15 +9,20 @@ body:
9
9
10
10
OpenShell is an agent-first project. Before filing this bug, point your coding agent at the repo and have it investigate using the available skills (`debug-openshell-cluster`, `debug-inference`, `openshell-cli`, etc.). See [CONTRIBUTING.md](https://github.com/NVIDIA/OpenShell/blob/main/CONTRIBUTING.md) for the full skills table.
11
11
12
+
Please also check the latest OpenShell release and search existing issues for possible duplicates before filing. If you cannot upgrade, retest, or search existing issues, explain why in the diagnostic.
13
+
12
14
- type: textarea
13
15
id: agent-diagnostic
14
16
attributes:
15
17
label: Agent Diagnostic
16
18
description: |
17
-
Paste the output from your agent's investigation of this bug. What skills did it load? What did it find? What did it try?
19
+
Paste the output from your agent's investigation of this bug. What skills did it load? What did it find? What did it try? Which OpenShell version did it test, and did it check the latest release, known fixes, and possible duplicates?
18
20
placeholder: |
19
21
Example:
20
22
- Loaded `debug-inference` skill
23
+
- Tested OpenShell v0.x.x
24
+
- Checked latest release / known fixes: no matching fix found
25
+
- Searched existing issues for duplicates: no matching issue found
21
26
- Ran `openshell inference get` and `openshell provider get ollama`
22
27
- Found `OPENAI_BASE_URL=http://127.0.0.1:11434/v1`, which is unreachable from the gateway
23
28
- Updated the provider to use `host.openshell.internal`, but the issue persists because the gateway is remote
@@ -47,11 +52,13 @@ body:
47
52
id: environment
48
53
attributes:
49
54
label: Environment
50
-
description: OS, Docker version, OpenShell version, and any other relevant details.
55
+
description: OS, Docker version, OpenShell version tested, whether the latest release and existing issues were checked, and any other relevant details.
Copy file name to clipboardExpand all lines: README.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
@@ -258,6 +258,8 @@ Telemetry events are limited to anonymous operational categories and counts, suc
258
258
259
259
Opting out applies only to telemetry emitted by OpenShell. Third-party services, model providers, inference endpoints, agents, or tools that you configure and use with OpenShell may have their own terms and privacy practices.
260
260
261
+
We publish aggregate usage trends from this telemetry every two weeks. See the [community telemetry reports](telemetry/README.md) for the latest summary.
262
+
261
263
## Notice and Disclaimer
262
264
263
265
This software automatically retrieves, accesses or interacts with external materials. Those retrieved materials are not distributed with this software and are governed solely by separate terms, conditions and licenses. You are solely responsible for finding, reviewing and complying with all applicable terms, conditions, and licenses, and for verifying the security, integrity and suitability of any retrieved materials for your specific use case. This software is provided "AS IS", without warranty of any kind. The author makes no representations or warranties regarding any retrieved materials, and assumes no liability for any losses, damages, liabilities or legal consequences from your use or inability to use this software or any retrieved materials. Use this software and the retrieved materials at your own risk.
0 commit comments