github-incident-from-recommendationslisted

Convert selected QA recommendations from devforgeai/qa/recommendations/STORY-NNN-qa-recommendations.md into GitHub issues in bankielewicz/DevForgeAI via gh issue create. Owns drafting, summary preview, drill-down approval flow, and posting. Consumes the embedded Github-incident-template.md as the issue-body schema and AI prompt. Use this skill whenever the user runs /create-incident-from-recommendations, asks to convert QA recommendations into GitHub issues, asks to "post issues from QA recs", asks to "create incidents from STORY-NNN findings", or wants to turn QA-validated findings into actionable GitHub work-orders. The skill is the only place in the framework that calls `gh issue create` for QA-recs-derived work — slash commands and other skills MUST delegate here rather than calling gh directly.
bankielewicz/DevForgeAI · ★ 4 · Code & Development · score 63

Install: claude install-skill bankielewicz/DevForgeAI

# github-incident-from-recommendations — Skill Definition This skill converts an array of QA recommendations (already parsed from `devforgeai/qa/recommendations/STORY-NNN-qa-recommendations.md` and selected upstream) into GitHub issues posted to `bankielewicz/DevForgeAI`. It owns drafting, preview, approval, and posting. The slash command `/create-incident-from-recommendations` delegates here for any work that touches `gh issue create`. **Sibling skill:** `github-incident-from-rca` (RCA-derived recs). Same posting pipeline, different input shape — QA recs are pre-structured (file, line, before_code, after_code, verification.command, classification) so drafting needs far fewer "Open Questions" inferences than the RCA path. **Embedded asset (the AI prompt that defines the issue body schema, quality bar, prohibited language, and DevForgeAI house rules):** - `assets/templates/Github-incident-template.md` — read this in Phase 1; it's the authoritative drafting prompt. Identical byte-for-byte to the sibling RCA skill's template. **Why a separate skill instead of inline command logic?** GitHub-issue creation has irreversible side effects (issues leave audit trails on the public repo). The framework's anti-pattern guidance treats irreversible-side-effect logic as a Layer-1 concern. Centralizing `gh issue create` in this skill (and its RCA sibling) gives one place to audit, version, and harden the posting path. --- ## When this skill is invoked The slash command `/create-incide