symphony-trello: Skill for Codex

Issue Sweep

This skill is a thin dispatcher. The canonical policy lives in ../../../docs/agents/github-issue-triage.md; do not duplicate the label matrix or issue editing rules here.

Workflow

1. Read ../../../docs/agents/github-issue-triage.md completely before fetching or editing issues. Treat it as the source of truth for sweep scope, issue-body updates, labels, dependencies, compatibility decisions, and already-implemented checks.
2. Confirm GitHub authentication and repository context with the active repository-approved GitHub tooling, such as the helper or app named by .tessl/RULES.md and installed GitHub skills. Do not use direct gh where those rules require helper or app access. If authentication is missing or editing is not permitted, report the blocker and do not pretend the sweep was completed.
3. Fetch all open issues, including title, body, labels, milestone, assignees, assignment timeline events, linked or referencing open pull requests, and relevant comments. Do not limit the sweep to examples named by the user.
4. Apply the canonical triage document in cycles. After making any change, fetch the open issue set again and repeat until one full pass finds no body, label, milestone, dependency, already-implemented, or relationship changes.
5. Write every issue you create or whose body you rewrite through the Issue forms section of ../../../docs/agents/github-issue-triage.md, and create follow-up issues before the final audit run so it covers them.
6. Handle comments by people on open and closed issues, pull requests, and Discussions as the canonical triage document's sweep rules say: reply, react, hide spam, answer paid-help and bounty offers, and post stale-assignment check-ins. Leave comments that need a maintainer decision for the report.
7. Prefer editing maintainer-authored issue bodies over adding comments, unless the canonical triage document calls for a historical comment or the issue was opened by another account.
8. End the sweep with the label audit from the repository root: node scripts/audit-issue-labels.ts. Fix every failure and rerun it until it reports none, then decide every judgment item as the canonical triage document's Label audit section says. The audit checks only the mechanical label rules; it does not replace step 4.
9. Finish with a concise report: number of cycles, issues changed, issues intentionally left unchanged, labels or dependencies repaired, users assigned from pickup comments, replies posted (person and comment URL), comments that got a 👍 instead of a reply, spam comments and bodies with their authors, comments left for the maintainer and the decision each needs, stale assigned issues with no open pull request and whether a check-in was posted, issues closed as already implemented, the final label audit output with the decision for each judgment item, and any blockers.