skills.rest
mono
monoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

bug-fix

Automate eight-phase bug investigation and resolution workflows for SkiaSharp C# bindings.

5.5k|644|Updated Feb 22, 2016
Search Tags:#workflow#debugging#reproduction#pull-request#bug-fix#skia#skiaSharp
One-click install
npx skills add https://github.com/mono/SkiaSharp --skill bug-fix-mono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-fix
Source: https://github.com/mono/SkiaSharp/tree/main/.github/skills/bug-fix
Command: npx skills add https://github.com/mono/SkiaSharp --skill bug-fix-mono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, step-by-step workflow to investigate, reproduce, diagnose, fix, and finalize bug fixes in SkiaSharp C# bindings.

Core Features & Use Cases

  • Structured multi-phase workflow with gate criteria, requiring a draft PR before investigation, and explicit reproduction and testing requirements.
  • Prerequisites and governance for bug fixes, including GitHub API access, Docker-based cross-platform testing, and standardized PR templates.
  • Comprehensive investigation lifecycle from issue understanding through finalizing PRs with linked fixes.

Quick Start

Follow the eight-phase bug-fix workflow to investigate, reproduce, fix, test, and finalize a SkiaSharp issue.

Frequently Asked Questions about bug-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix SkiaSharp C# binding bugs across different platforms?▼

Fixing SkiaSharp C# binding bugs requires an end-to-end workflow covering reproduction, root-cause analysis, minimal fixes, regression tests, and PR finalization across platforms. This process uses an eight-phase workflow with mandatory phase gates to ensure complete resolution.

What is the best way to reproduce a SkiaSharp issue before writing a fix?▼

The best way to reproduce a SkiaSharp issue is by using Docker-based cross-platform testing. Reproduction is an explicit requirement in the structured bug-fix workflow, which mandates creating a draft PR before deep investigation begins.

Do I need GitHub API access to resolve SkiaSharp pull requests?▼

Yes, you need GitHub API access to resolve SkiaSharp pull requests. Prerequisites for this bug-fix governance process include GitHub access, Docker-based testing environments, and standardized PR templates to finalize linked fixes.

Why create a draft PR before investigating a SkiaSharp bug?▼

Creating a draft PR before investigating a SkiaSharp bug institutes structured governance and mandatory sequencing. This ensures that reproduction, root-cause analysis, regression tests, and the final minimal fix are properly linked and tracked through the workflow phase gates.

What are the limitations of automated SkiaSharp bug resolution?▼

Automated SkiaSharp bug resolution requires strict sequencing through eight phase gates, meaning you cannot skip reproduction or testing. Cross-platform testing relies on Docker, and finalizing PRs requires structured templates and GitHub access.

Can I use this bug-fix workflow for C# bindings other than SkiaSharp?▼

This bug-fix workflow is specifically tailored for SkiaSharp C# bindings, covering Skia-specific reproduction and root-cause analysis. While the eight-phase structure is broadly applicable, its prerequisites and testing focus on SkiaSharp platforms.

Related Skills

Explore More Software Engineering Skills→
pekralpekral
5

auto-fix-bug

Automate bug fixing workflows from reproduction to GitHub PR.

Community
Advanced
greenheadHQgreenheadHQ
4

create-pr

Generate eight-section pull request bodies with ADR decision records.

Community
Advanced
ngocsangyemngocsangyem
14

meow:debug

Reproduce, isolate, root-cause, fix, and verify bugs with structured debugging.

Community
Intermediate
joegoldinjoegoldin
2

systematic-debugging

Apply a 4-phase debugging process for root cause analysis and hypothesis testing.

Community
Advanced