workflow-audit-emit-issues

workflow-audit-emit-issues

Files codebase audit findings as grouped GitHub issues — one issue per subsystem, sub-sectioned by domain.

When to invoke

After a codebase audit has produced a ranked findings table and the user accepts the "File as issues?" offer emitted by the audit-codebase command. Requires ≥1 finding in the orchestrator's context.

When NOT to invoke

• Zero findings — the audit ends at the rendered table; no offer is made.
• Without a preceding audit — this skill consumes in-context finding data only.
• To re-run the audit itself — see swe-workbench:workflow-codebase-audit (read-only; no back-edge here).

Composition

This skill is the filing counterpart to (not a caller of) swe-workbench:workflow-codebase-audit. Filing logic mirrors swe-workbench:workflow-bug-triage Phase 4 precedent: --body-file, .cmd sidecar, preview-gate-then-confirm. Template and label discovery follows the same chain used by agents/product-manager.md.

Input

Findings already in the orchestrator's context from the audit render. Each finding carries: file_line, domain, severity, confidence, effort, symptom, root_cause, reasoning_chain, counter_evidence_considered, suggested_fix.

Preamble — confirm runtime commands are on PATH

Confirm the plugin's runtime commands are reachable before any script call. If they are not on PATH (e.g. the plugin is not installed or predates bin/), abort loudly.

command -v swe-workbench-clean-state-files >/dev/null 2>&1 || {
  echo "swe-workbench runtime commands not on PATH — reinstall or update the swe-workbench plugin." >&2
  exit 1
}

Phases

Phase 1 — Group by subsystem

For each finding derive a subsystem from file_line:

1. Take the directory portion of the path (strip the filename).
2. Use up to the first 2 path segments as the grouping key.
3. Display label = last segment of that key:
   • src/auth/handler.ts → key src/auth → label auth
   • commands/audit-codebase.md → key commands → label commands
   • scripts/validate.py → key scripts → label scripts
4. Root-level file (directory portion is empty, e.g. README.md) → subsystem root.
5. No path (tool-level or unknown finding) → subsystem misc.