Thank you for your interest in contributing to SkiaSharp! This document provides guidelines for submitting issues and pull requests.

Before contributing, please review:

• documentation/dev/ - Architecture, memory management, and contributor guides
• documentation/dev/adding-apis.md - Complete guide for adding APIs
• documentation/dev/building.md - Build instructions

If you think you've found a bug, please check the Issues page first to see if an issue has already been filed. This helps reduce duplicate reports.

1. Validate that the issue is not resolved with the latest stable, pre-release, or nightly builds
2. Create a minimal reproduction project using only the code necessary to reproduce the issue
3. Clean your solution before compressing:
   • Delete all bin/ and obj/ folders
   • Remove the packages/ folder
   • Example structure to clean:

     [ProjectRoot]/ProjectName/bin
     [ProjectRoot]/ProjectName/obj
     [ProjectRoot]/ProjectName.Android/bin
     [ProjectRoot]/ProjectName.Android/obj
     [ProjectRoot]/ProjectName.iOS/bin
     [ProjectRoot]/ProjectName.iOS/obj
     [ProjectRoot]/ProjectName.UWP/bin
     [ProjectRoot]/ProjectName.UWP/obj
     

• Platform information: Note if the issue occurs only on specific platforms
• Regressions: If applicable, identify the last working build version
• Device specifics: Some issues occur only on specific:
  • Device types (phones, tablets, desktops)
  • OS versions
  • Target SDK versions
  • Physical devices vs simulators/emulators
• Upload reproductions: Attach reproduction projects directly to the issue (don't use external file sharing)

We greatly welcome PRs with fixes and improvements from the community!

1. Follow existing patterns - Study similar APIs before adding new ones
2. Add tests - All new features and bug fixes should include tests
3. Update documentation - If you're changing public APIs
4. Memory management - Ensure proper disposal and pointer type handling (see documentation/dev/memory-management.md)
5. Error handling - Validate parameters and handle errors appropriately (see documentation/dev/error-handling.md)

Follow the comprehensive guide in documentation/dev/adding-apis.md, which covers:

• Analyzing C++ APIs and identifying pointer types
• Creating C API wrappers
• Writing P/Invoke declarations
• Implementing C# wrapper classes
• Testing your changes

• Dispose pattern: Always use using statements in samples and tests
• Parameter validation: Validate all parameters in C# before P/Invoke
• Error checking: Check return values from C API calls
• Memory safety: Understand pointer types (see documentation/dev/memory-management.md)
• Naming conventions: Follow existing naming patterns (see documentation/dev/architecture.md)

• .NET 8 SDK - The repo is pinned via global.json
• MAUI workload - Required for mobile targets:

  dotnet workload install maui

If you're only making changes to managed code:

# Download pre-built native libraries
dotnet cake --target=externals-download

# Build managed libraries
dotnet cake --target=libs

# Run tests
dotnet cake --target=tests

For faster iteration when working on binding code:

dotnet build tests/SkiaSharp.Tests.Console/SkiaSharp.Tests.Console.csproj
dotnet test tests/SkiaSharp.Tests.Console/SkiaSharp.Tests.Console.csproj

See documentation/dev/building.md for complete build instructions.

For native code changes, see:

• documentation/dev/building.md - Windows & macOS
• documentation/dev/building-linux.md - Linux

• documentation/dev/ - Complete collection of contributor documentation
• Maintainer guides - See documentation/dev/maintaining.md
• Release process - See documentation/dev/releasing.md

• Architecture questions: Review documentation/dev/
• Build issues: Check documentation/dev/building.md
• API usage: Check the API documentation
• Still stuck? Open an issue with your question

Your contributions make SkiaSharp better for everyone. We appreciate your time and effort!