git:20260914.ceaddf0 to git:20260916.72cc245

15 added, 18 removed. Audit A to A.

---

name: github-issue-triage

description: Prioritize open issues and establish acceptance criteria before marking them ready for development.

triggers:

- /github-issue-triage

---

# GitHub issue triage

Prioritize open issues and establish acceptance criteria before marking them ready for development.

- Create this automation separately from implementation and review. Select an agent

- profile on its definition. The profile owns the model, tools, and `secret_refs`;

- this workflow does not choose a profile or discover credentials from host settings.

- Use a fine-grained GitHub PAT limited to the selected repositories with

- Issues: read and write. Store it in the Agent Server secret store and select its name in

- the profile. Never put the token value in the automation definition or prompt.

+ Create this automation separately from implementation and review. Use a

+ fine-grained GitHub PAT limited to the selected repositories with Issues: read and

+ write. Never put the token value in the automation definition or prompt.

- Package the files in this skill’s `scripts/` directory together.

- `github_client.py` is installed alongside `worker.py` from the shared GitHub source.

- The catalog bundle declares these exact files. Supply `config.json` with `repos`

- (an array of `owner/repo` names). The entrypoint is `python3 worker.py

- --github-token-secret GITHUB_PERSONAL_ACCESS_TOKEN`; if the selected profile uses

- another secret name, pass that name instead. Naming a secret does not grant it:

- the Agent Server only supplies secrets allowed by the profile.

+ Package `worker.py` with the shared `github_client.py` and

+ `agent_conversation.py` helpers. Supply `config.json` with `repos` and the saved

+ GitHub secret name; the entrypoint is `python3 worker.py`. Include that secret in

+ the selected profile so the delegated agent can use GitHub. Naming it in the

+ automation does not grant it to the agent.

- The same bundle runs in local and Docker workspaces. The Automation Service

- provides the conversation, workspace, and scoped server connection; it owns

- scheduling, concurrency, cancellation, and cleanup.

+ The scanner is an ordinary Automation host command. It submits selected issues

+ through the shared KV-backed conversation dispatcher, which creates or resumes

+ one stable conversation per issue through the Software Agent SDK. Only that

+ agent workspace is local or Docker. Automation owns scheduling, cancellation,

+ and cleanup.

Honor `Depends on: #12, #13` lines. A dependency must be closed as completed.

Post readable acceptance criteria and rationale. Add `ready-for-dev` only when

criteria are actionable; preserve existing issue labels. Unclear issues stay open

for clarification. Do not implement code or accept pull requests.

- Each scheduled run triages at most one changed issue per repository. Choose the

- schedule frequency accordingly when processing an existing backlog.

+ Each scheduled run submits every changed eligible issue. A failure on one issue is

+ reported and does not prevent the remaining issues from being submitted.