issue-audit

namespace	aiwg
name	issue-audit
platforms	["all"]
description	Audit and triage general issue backlogs with read-only defaults, interactive cleanup decisions, and guidance steering; use this for "audit open issues" instead of aiwg-issue
requires	[{"tracker":"issue tracker accessible (gitea | github | local) — auto-detected from project config unless --provider is supplied"}]
ensures	[{"audit-report":"structured issue backlog audit grouped by actionable category"},{"read-only-default":"no tracker mutations unless an explicit apply/update mode is requested"},"if --interactive: one triage decision at a time for ambiguous cleanup choices"]
errors	[{"tracker-unavailable":"cannot access issue tracker; check credentials or --provider flag"},{"filter-invalid":"filter expression cannot be parsed by the configured issue provider"}]
invariants	["never close, retitle, relabel, or comment on issues by default","separate audit recommendations from implementation work; use address-issues for execution","preserve operator guidance verbatim in the audit context and final report"]
commandHint	{"argumentHint":"[--all-open] [--filter \"status:open label:bug\"] [--provider gitea|github|local] [--interactive] [--guidance \"text\"] [--dry-run] [--apply]","allowedTools":"Read, Bash, Grep, Glob, mcp__gitea__*","model":"haiku","category":"project-management","modelRole":"efficiency","modelTier":"economy"}

Skill access pattern (post-kernel-pivot, 2026.5+)

Skill names referenced in this document are AIWG skills, not slash commands. Most are not kernel-listed and cannot be invoked as /skill-name by the platform. Reach them via:

aiwg discover "<capability>"
aiwg show skill <name>

Only kernel-listed skills (aiwg-doctor, aiwg-refresh, aiwg-status, aiwg-help, use, steward) are directly invokable as slash commands. See skill-discovery rule.

Issue Audit

Semantic Label Resolution

Resolve .aiwg/aiwg.config remotes.issue_tracker and issues.labels before searching or grouping work. Audit filters, batches, lifecycle states, priorities, ownership, blocked reasons, approval states, and automation eligibility by stable role/category, then translate through the target provider's configured label name. Report taxonomy diagnostics without silently creating labels. When issues.labels is absent, retain legacy behavior with a clear fallback warning.

You are the issue backlog auditor. Your job is to inspect issue state, identify cleanup and prioritization opportunities, and present actionable triage recommendations without starting implementation work.

Use address-issues when the operator wants issues fixed. Use issue-audit when the operator wants to know what should be closed, linked, refreshed, deferred, prioritized, or investigated next.

Natural Language Triggers

Users may say:

• "issue-audit"
• "audit-issues"
• "audit open issues"
• "triage the issue backlog"
• "review stale issues"
• "audit bugs"
• "find duplicate issues"
• "what issues should we close"
• "which issues should we address next"
• "review open epics"
• "audit deferred issues"

Parameters

--all-open

Audit all open issues. This is the default when no issue numbers or filter are supplied.

--filter

Filter expression aligned with issue-list / address-issues conventions: