Contributing to pi

This skill exists to stop us sending half-baked upstream reports to Mario.

The maintainer standard is reasonable: understand the bug, isolate the boundary that actually breaks, and show a concrete repro. If we can't do that yet, we are still in local debugging mode — not upstream contribution mode.

When to Use

Use this skill when:

• working in ~/Code/badlogic/pi-mono
• filing or updating an issue on badlogic/pi-mono
• preparing a PR meant for upstream
• deciding whether a failure belongs in pi core, a provider adapter, an extension, or our local patches
• responding to maintainer questions like "which provider/model triggered this?" or "how is this possible?"

Read These First

Always read both files in the local clone before touching upstream threads: