Issue Ops extends reviewer workflows into backlog operations. It helps maintainers spot stale or no-longer-applicable infra blockers, but keeps final decisions human-owned.
Why This Exists
Issue lists decay fast: old infra blockers stay open, linked PR context drifts, and teams lose confidence in the backlog. Issue Ops gives maintainers one triage surface where every recommendation includes a confidence score and explainable signals.
Board Overview
The project view below is optimized for issue triage at scale. You can quickly separate likely-invalid blockers from items that still need active ownership.
Signals That Matter
Each issue recommendation includes:
Issue Review Action(close,keep-open,needs-human-review)Issue Review Action Confidence(0-100, with high/medium/low levels)- linked PR context (
Matched Pull Request, related PRs) - supporting confidence signals (stale age, reopen history, activity recency)
Safety First
Issue Ops is assistive, not autonomous governance.
- Do not run unattended close/merge decisions in production.
- Use dry-run and proposal-only passes first.
- Require a maintainer-owned approval step for mutating actions.
Start Here
intelligencex todo project-bootstrap --repo owner/repo --owner owner
intelligencex todo issue-review --repo owner/repo --proposal-only --min-consecutive-candidates 2
intelligencex todo project-sync --config artifacts/triage/ix-project-config.json --issue-review artifacts/triage/ix-issue-review.json --dry-run