searxng-mcp-go/docs/agents/issue-tracker.md
opencode-agent[bot] 1def765bba Made issue tracker cmds JSON-parseable
Co-authored-by: xlionjuan <[email protected]>
2026-06-12 20:13:48 +00:00

1.7 KiB

Issue tracker: GitHub

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

Conventions

  • Create an issue: gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies.
  • Read an issue: gh issue view <number> --json number,title,body,labels,comments --jq '{number, title, body, labels: [.labels[].name], comments: [.comments[].body]}'
  • List issues: gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]' with appropriate --label and --state filters.
  • Comment on an issue: gh issue comment <number> --body "..."
  • Apply / remove labels: gh issue edit <number> --add-label "..." / --remove-label "..."
  • Close: gh issue close <number> --comment "..."

Infer the repo from git remote -v — gh does this automatically when run inside a clone.

Before applying or removing labels, read docs/agents/triage-labels.md. Labels accepted, needs-explain, and rejected are human-only decision labels; do not change them unless the user explicitly requests that exact label operation.

When a skill says "publish to the issue tracker"

Create a GitHub issue.

When a skill says "fetch the relevant ticket"

Run gh issue view <number> --json number,title,body,labels,comments --jq '{number, title, body, labels: [.labels[].name], comments: [.comments[].body]}'.

Pull requests

For branch and PR work, also read docs/agents/pull-requests.md. PR agents must ignore REPORT.md unless explicitly asked for a local report, and every PR body must mention related documentation updates or explain why none were needed.