Skill Claude CodeCodex
Use for every hardware bring-up or debug session that ports mainline Linux to a phone or tablet. Retail-unlock targets require an already-unlocked bootloader; locked retail bootloaders are out of scope. Exploit-booted and firmware-booted targets require a demonstrated boot path; the skill never provides unlock or…
Command Claude Code
Capture all available evidence from the device before changing anything (phase 1 of linux-phone-porting).
Command Claude Code
Gate a fix before it costs a flash (phase 3 of linux-phone-porting).
Command Claude Code
Iterate research → implement → verify autonomously until a capability works or the model of it is exhausted (linux-phone-porting).
Command Claude Code
Research a requested change against the device and every source family before building it (phase 2 of linux-phone-porting, capability framing).
Command Claude Code
Establish the target and take the pre-flash backup that later research depends on (phase 0 of linux-phone-porting).
Command Claude Code
Research a symptom or a new capability across every source family before writing any code (phase 2 of linux-phone-porting).
Command Claude Code
Update an installed linux-phone-porting skill and its companion commands without discarding local work (maintenance outside the hardware phases).
Command Claude Code
Prepare, submit and track an upstream contribution from port work (linux-phone-porting).
Command Claude Code
Use when disk pressure or an explicit operator request calls for cleaning a Linux-phone porting workspace — stale artifacts, old shared kernel/OS bases, abandoned build outputs, stale result links and package-store closures (host-side workspace maintenance, outside the hardware phases).
Command Claude Code
Bring the port's kernel, firmware, userspace and other components to newer releases in one governed pass (linux-phone-porting).
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: