mirror of
https://github.com/NVIDIA/OpenShell.git
synced 2026-10-29 07:23:25 +08:00
* docs: enhance AGENTS.md as primary agent entrypoint Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * chore: add opencode agent definitions for sub-agent workflows Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * docs: overhaul CONTRIBUTING.md for agent-first workflow Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * docs: reframe README.md with agent-first identity Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * chore: add bug report and feature request issue templates Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * chore: add issue template config with agent-first contact links Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * chore: add pull request template Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * chore: add CODEOWNERS Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * chore: update .claude/ README to document skill symlink and consolidation Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * chore: remove github-rest-api skill Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * feat: add triage-issue skill for community issue assessment Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * refactor: update create-github-issue skill for template conformance Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * refactor: update create-github-pr skill for template conformance Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * refactor: update build-from-issue skill for template conformance and triage awareness Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * ci: add issue triage gate workflow Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> * feat: add sync-agent-infra skill to detect and fix infrastructure drift Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com> --------- Signed-off-by: John Myers <9696606+johntmyers@users.noreply.github.com>
3.2 KiB
3.2 KiB
name, description
| name | description |
|---|---|
| create-github-issue | Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue. |
Create GitHub Issue
Create issues on GitHub using the gh CLI. Issues must conform to the project's issue templates.
Prerequisites
The gh CLI must be authenticated (gh auth status).
Issue Templates
This project uses YAML form issue templates. When creating issues, match the template structure so the output aligns with what GitHub renders.
Bug Reports
Use the bug label. The body must include an Agent Diagnostic section — this is required by the template and enforced by project convention.
gh issue create \
--title "bug: <concise description>" \
--label "bug" \
--body "$(cat <<'EOF'
## Agent Diagnostic
<Paste the output from the agent's investigation. What skills were loaded?
What was found? What was tried?>
## Description
**Actual behavior:** <what happened>
**Expected behavior:** <what should happen>
## Reproduction Steps
1. <step>
2. <step>
## Environment
- OS: <os>
- Docker: <version>
- OpenShell: <version>
## Logs
Feature Requests
Use the feat label. The body must include a Proposed Design — not a "please build this" request.
gh issue create \
--title "feat: <concise description>" \
--label "feat" \
--body "$(cat <<'EOF'
## Problem Statement
<What problem does this solve? Why does it matter?>
## Proposed Design
<How should this work? Describe the system behavior, components involved,
and user-facing interface.>
## Alternatives Considered
<What other approaches were evaluated? Why is this design better?>
## Agent Investigation
<If the agent explored the codebase to assess feasibility, paste findings here.>
EOF
)"
Tasks
For internal tasks that don't fit bug/feature templates:
gh issue create \
--title "<type>: <description>" \
--body "$(cat <<'EOF'
## Description
<Clear description of the work>
## Context
<Any dependencies, related issues, or background>
## Definition of Done
- [ ] <criterion>
EOF
)"
Useful Options
| Option | Description |
|---|---|
--title, -t |
Issue title (required) |
--body, -b |
Issue description |
--label, -l |
Add label (can use multiple times) |
--assignee, -a |
Assign to user |
--milestone, -m |
Add to milestone |
--project, -p |
Add to project |
--web |
Open in browser after creation |
After Creating
The command outputs the issue URL and number.
Display the URL using markdown link syntax so it's easily clickable:
Created issue [#123](https://github.com/OWNER/REPO/issues/123)
Use the issue number to:
- Reference in commits:
git commit -m "Fix validation error (fixes #123)" - Create a branch following project convention:
<issue-number>-<description>/<username>