garura:capture

To automatically file structured GitHub issues, this Skill converts title and problem inputs into type-driven markdown issue bodies and dispatches them asynchronously. It formats metadata tables, applies required labels, and handles network failures with a local fallback.

Yes, you can infer GitHub issue types from problem text. When an explicit type is not provided, the Skill infers the issue type from the problem statement, applying special handling rules for defect severity and resolving ambiguous inferences.

The best way to capture production incident reports is providing a title and problem statement to this Skill. It infers the defect type, enforces required severity fields, formats a structured markdown body, and dispatches a labeled GitHub issue asynchronously.

Fallback handling during issue dispatch activates when GitHub is unreachable. The Skill creates a portable local fallback file containing the formatted issue data, ensuring no structured capture inputs are lost during asynchronous network failures.

You do not need to provide evidence and root cause sections to file a GitHub issue. The Skill requires only a title and problem statement, while evidence, root cause, specific issues, expected behavior, and impact are optional inputs.

Async dispatch matters for GitHub issue filing because it prevents blocking the caller during network requests. This allows agents or human callers to capture and submit structured issues immediately without waiting for GitHub API responses.