github-incident-from-rca
Converts RCA recommendations into tracked GitHub issues using a standardized template and approval flow.
Install
mkdir -p .claude/skills/github-incident-from-rca && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12783" && unzip -o skill.zip -d .claude/skills/github-incident-from-rca && rm skill.zipInstalls to .claude/skills/github-incident-from-rca
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Convert selected RCA recommendations 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-rca, asks to convert RCA recommendations into GitHub issues, asks to "post issues from RCA", asks to "create incidents from RCA recommendations", or wants to turn analysis findings into actionable GitHub work-orders. The skill is the only place in the framework that calls `gh issue create` for RCA-derived work — slash commands and other skills MUST delegate here rather than calling gh directly.Key capabilities
- →Convert selected RCA recommendations into GitHub issues
- →Draft issue bodies using a predefined template
- →Provide a summary preview of the drafted issues
- →Manage an approval flow for issue posting
- →Post issues to the bankielewicz/DevForgeAI repository
- →Validate input recommendations against a schema
How it works
The skill takes structured RCA recommendations, drafts GitHub issue bodies using a template, and posts them to a specific repository after an approval process.
Inputs & outputs
When to use github-incident-from-rca
- →Create issues from RCA findings
- →Convert incident analysis into tasks
- →Track incident follow-up work
About github-incident-from-rca
Parses RCA recommendations and creates formatted GitHub issues in the DevForgeAI repository. It manages the drafting, previewing, and posting of these issues with a strict approval gate.
Convert selected RCA recommendations 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 ru
When not to use it
- →When creating GitHub issues not derived from RCA recommendations
- →When posting issues to a repository other than bankielewicz/DevForgeAI
- →When bypassing the approval flow for issue creation
Prerequisites
Limitations
- →Issues are posted only to the bankielewicz/DevForgeAI repository.
- →The skill requires `gh` CLI authentication.
- →Issue body size is limited by GitHub's ~64KB limit.
How it compares
This skill provides a controlled, auditable, and structured workflow for converting RCA findings into GitHub issues, ensuring adherence to a specific schema and requiring explicit approval before posting.
Compared to similar skills
github-incident-from-rca side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| github-incident-from-rca (this skill) | 0 | 1mo | Review | Intermediate |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| python-code-style | 9 | 6mo | Review | Intermediate |
| code-review-excellence | 19 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by bankielewicz
View all by bankielewicz →You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
code-review-excellence
wshobson
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
code-walk-thru
pchalasani
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
schema-markup
davila7
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.