incident-to-issue

To turn incident data into a GitHub Issue, the skill automates structuring symptoms, detection time, impact, and provisional fixes into a ready-to-post Issue body with mandatory labels and sections for blameless postmortem workflows.

The best way to document a blameless postmortem in GitHub Issues is to use a structured template that captures symptoms, timeline, impact, root cause hypotheses, and mitigating actions, ensuring knowledge is preserved and traceable.

You create a consistent incident response issue template by providing a defined incident payload, which the skill uses to generate an Issue body with mandatory labels and sections that connect to ADRs and guide subsequent plan-time work.

You need a defined incident payload containing symptoms, detection time and path, affected scope, provisional workarounds, and resource links to generate a complete and traceable GitHub Issue.

Yes, you can use it to capture detection details and provisional fixes for retrospective work, as the skill structures these inputs into a structured GitHub Issue to preserve learnings and guide subsequent plan-time work.

Yes, the skill works without dependencies to create incident response issues, requiring only a defined incident payload to output a ready-to-post GitHub Issue body with mandatory labels and sections.