lineageos

Automate LineageOS source syncing, device builds, and Gerrit patch submissions.

32|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/hyperb1iss/hyperdroid-skill --skill lineageos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lineageos
Source: https://github.com/hyperb1iss/hyperdroid-skill/tree/main/skills/lineageos
Command: npx skills add https://github.com/hyperb1iss/hyperdroid-skill --skill lineageos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

LineageOS development workflows are complex, involving syncing multiple repositories, building device-specific images, and coordinating patch contributions, often leading to fragmented, error-prone processes.

Core Features & Use Cases

  • Sync LineageOS sources across repositories with repo and manifest management
  • Build device images using breakfast/brunch and related tooling
  • Submit changes via Gerrit using repopick and proper commit workflows
  • Suitable for maintainers, developers, and ROM contributors coordinating multi-device projects

Quick Start

Initialize the LineageOS workspace, sync sources for your target branch, set up the environment, and start a device build.

Frequently Asked Questions about lineageos

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

FAQPage Schema
How do I sync LineageOS source repositories for a specific branch?

You sync LineageOS sources by using repo and manifest management to initialize the workspace and pull repositories for your target branch across the entire project.

What is the best way to build a LineageOS device image?

The best way to build a LineageOS device image is by setting up the environment and using breakfast to configure the device target, followed by brunch to compile the ROM.

How do I submit LineageOS patches via Gerrit?

You submit LineageOS patches via Gerrit by using repopick for patch retrieval and following proper commit workflows to push code reviews for your device tree changes.

Do I need a standard source layout to manage multi-device LineageOS builds?

Yes, you need a standard LineageOS source layout along with repo tooling and Gerrit-based patch workflows to enable end-to-end multi-device builds and reviews.

Why does the LineageOS build workflow require coordinating multiple repositories?

The LineageOS build workflow requires coordinating multiple repositories because device trees, manifests, and source code are fragmented across separate repos, making manual syncing error-prone.